[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Bug: error enlighting file: [8.0-pre (release_8.0-pre-335-g4c426
From: |
Suvayu Ali |
Subject: |
Re: [O] Bug: error enlighting file: [8.0-pre (release_8.0-pre-335-g4c426b-git @ org-loaddefs.el can not be found!)] |
Date: |
Mon, 15 Apr 2013 18:22:39 +0200 |
User-agent: |
Mutt/1.5.21 (2012-12-30) |
On Mon, Apr 15, 2013 at 06:05:56PM +0200, Suvayu Ali wrote:
> Hi Bastien,
>
> On Mon, Apr 15, 2013 at 05:49:28PM +0200, Bastien wrote:
> > Suvayu Ali <address@hidden> writes:
> >
> > > BTW, to others, is it by any chance possible to check how emacs was
> > > started (if -q or -Q was present among the command line options)? Then
> > > a message could be shown about minimal testing with a setup when users
> > > call `org-submit-bug-report'.
> >
> > Well, there is `command-line-args' but -Q is deleted from this list
> > when the args are processed.
>
> As far as I recall, if you start with emacs -Q, then customize refuses
> to save anything. Not sure if this is true for -q too. That would
> imply customize source should have some hint on how to do that :).
I took a peek at the source; you can test for custom-file. Take a look
at custom-save-variable. Here is the snippet I'm alluding to:
...
(if (custom-file t)
(custom-save-all)
(message "Setting `%s' temporarily since \"emacs -q\" would overwrite
customizations"
variable)
(set variable value))
...
Hope this helps,
:)
--
Suvayu
Open source is the future. It sets us free.