From: Lars Ingebrigtsen <larsi@gnus.org>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: 16242@debbugs.gnu.org
Subject: bug#16242: 24.3; wish: set init directory (.emacs.d) by commandline flag for easy custom environments
Date: Wed, 14 Aug 2019 19:12:57 -0700 [thread overview]
Message-ID: <87k1bf6us6.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87ppom45ge.wl%arne_bab@web.de> (Arne Babenhauserheide's message of "Tue, 24 Dec 2013 16:46:41 +0100")
Arne Babenhauserheide <arne_bab@web.de> writes:
> There are nowadays quite a few customized Emacs environments (like
> prelude, emacs-for-python, elpy, and so forth), and testing them
> quickly can be quite a challenge, because they need to be intergrated
> with the local customizations.
>
> To ease that, it would be nice, if I could simply set the directory to
> use for my init with a commandline flag.
>
> This would make it possible to specialize my local emacs in several
> different ways - and to quickly show not-yet-emacs-users how emacs
> would work for their task:
>
> emacs --init-dir ~/emacs-init/python-ide # edit python
(I'm going through old bug reports that have unfortunately gotten no
responses yet.)
I think this sounds like a reasonable request, and I was surprised that
this doesn't exist yet.
You can achieve something like this with, for instance,
HOME=/tmp/foo emacs ...
or with --eval, but neither seem very logical.
Does anybody object to adding an --init-dir switch? It would just
basically set `user-emacs-directory'.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-15 2:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 15:46 bug#16242: 24.3; wish: set init directory (.emacs.d) by commandline flag for easy custom environments Arne Babenhauserheide
2019-08-15 2:12 ` Lars Ingebrigtsen [this message]
2019-08-15 4:18 ` Glenn Morris
2019-08-15 4:33 ` Lars Ingebrigtsen
2019-08-15 14:29 ` Noam Postavsky
2019-08-15 23:13 ` Lars Ingebrigtsen
2022-01-26 16:44 ` Lars Ingebrigtsen
2022-01-27 10:20 ` Andrea Corallo
2022-01-27 15:58 ` Lars Ingebrigtsen
2022-01-27 22:36 ` Lars Ingebrigtsen
2022-01-27 23:30 ` Glenn Morris
2019-08-15 14:44 ` 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=87k1bf6us6.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=16242@debbugs.gnu.org \
--cc=arne_bab@web.de \
/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).