From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: 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 [thread overview]
Message-ID: <20130415162239.GJ16442@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <20130415160556.GH16442@kuru.dyndns-at-home.com>
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 <fatkasuvayu+linux@gmail.com> 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.
prev parent reply other threads:[~2013-04-15 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 0:24 Bug: error enlighting file: [8.0-pre (release_8.0-pre-335-g4c426b-git @ org-loaddefs.el can not be found!)] David Arroyo Menéndez
2013-04-12 6:51 ` Nicolas Goaziou
2013-04-15 7:05 ` Suvayu Ali
2013-04-15 15:49 ` Bastien
2013-04-15 16:05 ` Suvayu Ali
2013-04-15 16:22 ` Suvayu Ali [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130415162239.GJ16442@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).