From: Juri Linkov <juri@jurta.org>
Cc: larsh@soem.dk, ams@gnu.org, raeburn@raeburn.org, emacs-devel@gnu.org
Subject: Re: --no-desktop broken?
Date: Mon, 23 Jan 2006 08:18:31 +0200 [thread overview]
Message-ID: <87fynf32w8.fsf@jurta.org> (raw)
In-Reply-To: <u3bjfpmgu.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 23 Jan 2006 07:00:49 +0200")
> ;; We cannot use `command-switch-alist' to process "--no-desktop" because these
> ;; functions are processed after `after-init-hook'.
>
> The above comment explains why this is not a good idea.
Yes, I'm already aware of this comment. That's why I haven't proposed to use
`command-switch-alist' directly to process "--no-desktop".
> All of these solutions will load desktop.el (and what's worse, load it
> unconditionally, I think), which I think is not a good design.
Only the first solution loads desktop.el, and I agree that it is not
a good solution. The remaining two solutions don't load desktop.el.
They use the autoload cookie. This means that at the time startup.el
starts processing command switches, it already has "--no-desktop"
in `command-switch-alist' without loading desktop.el. The effect is
exactly the same as adding "--no-desktop" to the local variable
`longopts' in `command-line-1'. I think not using package-specific
switches in startup.el gives better modularity.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2006-01-23 6:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 0:48 --no-desktop broken? Alfred M. Szmidt
2006-01-21 9:35 ` Eli Zaretskii
2006-01-21 9:38 ` Lars Hansen
2006-01-21 23:53 ` Ken Raeburn
2006-01-22 11:32 ` Lars Hansen
2006-01-23 1:51 ` Juri Linkov
2006-01-23 5:00 ` Eli Zaretskii
2006-01-23 6:18 ` Juri Linkov [this message]
2006-01-23 8:24 ` Lars Hansen
2006-01-23 22:54 ` Eli Zaretskii
2006-01-23 23:43 ` Lars Hansen
2006-01-24 4:24 ` Eli Zaretskii
2006-01-24 15:02 ` Lars Hansen
2006-01-23 23:00 ` Eli Zaretskii
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=87fynf32w8.fsf@jurta.org \
--to=juri@jurta.org \
--cc=ams@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsh@soem.dk \
--cc=raeburn@raeburn.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.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).