unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: [Emacs-diffs] emacs/lisp/org org.el ChangeLog
Date: Wed, 2 Sep 2009 11:32:08 +0200	[thread overview]
Message-ID: <6E35F7BC-62C1-47DD-981C-84CE53296A5A@gmail.com> (raw)
In-Reply-To: <jwvtyzmhccv.fsf-monnier+emacs@gnu.org>


On Sep 1, 2009, at 6:17 PM, Stefan Monnier wrote:

>> I have my default-major-mode set to `org-mode'.
>
>> In the function where you placed your comment, I am calling
>> customize-save-variable.  IIRC, it happened to me that my custom
>> file did not have a .el extension, and that, when the custom file
>> was visited in order to write the modified variable, org-mode
>> was selected for that file and messed it up, somehow.
>
>> I don't know if this could still happen, but I believe
>> this was the issue, and to be safe I scoped a the default
>> value for default-major-mode into that call.
>
>> What do you want me to do about it?
>
> Report a bug for it.

I will, if that happens to me again.

>
>> Remove it and hope for the best, or explain it in a commentary?
>
> I don't have any strong opinion on it (other than the fact that
> default-major-mode should be replaced by (default-value 'major-mode),
> which is a bit more troublesome in let), but if you keep it, then  
> please
> add a comment explaining that it's a workaround for a bug in cutomize
> (or somesuch).

OK, I got rid of this in my development version, and I will push my
changes to Emacs soon.

- Carsten


>
>
>        Stefan





      reply	other threads:[~2009-09-02  9:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1MhPCj-0000qh-TC@cvs.savannah.gnu.org>
2009-09-01  6:49 ` [Emacs-diffs] emacs/lisp/org org.el ChangeLog Carsten Dominik
2009-09-01 16:17   ` Stefan Monnier
2009-09-02  9:32     ` Carsten Dominik [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6E35F7BC-62C1-47DD-981C-84CE53296A5A@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).