From: Hans BKK <hansbkk@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: setting default font name
Date: Tue, 20 May 2014 06:32:40 -0700 (PDT) [thread overview]
Message-ID: <4208f504-fdd5-4b2a-8340-0c7b363797aa@googlegroups.com> (raw)
In-Reply-To: <87egzrz5c2.fsf@bach.histomat.net>
Haines Brown wrote:
> I finally am able to open an emacs session that relies on
> **a custom init file** using the -q -l options
>by setting the font in a session that is started without the -q option, and then save that font to its init file. Then I can copy that material to the init file used with the -q option.
There seem to be a lot of issues around the specific font issue, functions used, syntax etc that would be great to get isolated and correct solution posted FFR.
However I want to also point out the more general issue that you appear to not have completely absorbed from my and Drew's posts above - see my emphasis above.
By launching with the -q option you are
A) instructing Emacs to launch without ANY init file at all, even if you then also load a script to be eval'd with the -l option - this is NOT the same as loading an init file.
And
B) explicitly instructing Emacs to NOT save any configuration changes made through the Customize facility - as you are informed by a warning message at startup.
Launching instances of emacs either via another user's session or by scripting a different $HOME folder before launching emacs as in the thread I pointed out above is IMO a more straightforward way to test most config/init issues with clean slate to troubleshoot interference from other packages/scripts normally loaded in your production setup.
prev parent reply other threads:[~2014-05-20 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 11:36 setting default font name Haines Brown
2014-05-18 13:35 ` Drew Adams
[not found] ` <mailman.1565.1400420140.1147.help-gnu-emacs@gnu.org>
2014-05-18 21:11 ` Haines Brown
2014-05-18 21:57 ` Michael Heerdegen
2014-05-18 22:03 ` Drew Adams
[not found] ` <mailman.1582.1400450623.1147.help-gnu-emacs@gnu.org>
2014-05-19 11:09 ` Haines Brown
2014-05-19 13:47 ` Drew Adams
[not found] ` <mailman.1604.1400507269.1147.help-gnu-emacs@gnu.org>
2014-05-19 15:05 ` Haines Brown
2014-05-19 15:45 ` Drew Adams
[not found] ` <mailman.1615.1400514331.1147.help-gnu-emacs@gnu.org>
2014-05-19 18:56 ` Haines Brown
2014-05-19 20:51 ` Drew Adams
[not found] ` <mailman.1639.1400532700.1147.help-gnu-emacs@gnu.org>
2014-05-20 10:14 ` Jacob Gerlach
2014-05-20 10:58 ` Haines Brown
2014-05-19 19:30 ` Hans BKK
2014-05-20 13:32 ` Hans BKK [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=4208f504-fdd5-4b2a-8340-0c7b363797aa@googlegroups.com \
--to=hansbkk@gmail.com \
--cc=help-gnu-emacs@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.
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).