From: Oleh Krehel <ohwoeowho@gmail.com>
To: "François Févotte" <francois.fevotte@ensta.org>
Cc: 15539@debbugs.gnu.org
Subject: bug#15539: [PATCH] Setting user-emacs-directory
Date: Wed, 01 Apr 2015 18:48:52 +0200 [thread overview]
Message-ID: <87d23npzez.fsf@gmail.com> (raw)
In-Reply-To: <87384jhn9u.fsf@gmail.com> (Oleh Krehel's message of "Wed, 01 Apr 2015 17:38:21 +0200")
Oleh Krehel <ohwoeowho@gmail.com> writes:
> François Févotte <francois.fevotte@ensta.org> writes:
>
>> Hello,
>>
>> On Tue, Mar 24, 2015 at 12:25 AM, François Févotte <fevotte@gmail.com> wrote:
>>> below is a patch trying to address old bug #15539.
>>
>> after the lack of reaction to my last email, I would like to have one
>> more chance of getting emacs-devel's feedback on this issue (namely:
>> being able to tell Emacs where to find its init file).
>>
>> Is nobody interested in this feature? Or is the proposed patch not adequate?
>> In the former case, please just say so, so that we can maybe mark the
>> bug as "wontfix" and let it be clear. In the latter case, I'm still
>> welcoming any comment on the proposed solution. And of course I'm
>> willing to work on any improvement you might suggest.
>
> I'm interested in this feature, I just didn't have time to test it yet.
> I'll try to look at it soon.
OK, I've tested it and it works great. I vote for merging this if
someone is counting.
Just one question: why is `getenv' called twice?
Oleh
next prev parent reply other threads:[~2015-04-01 16:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAADsv94GP0tVZtsS0na6RWtOc+WpDDAYDZqw299hw6j5Rq8sUw@mail.gmail.com>
2015-04-01 15:24 ` bug#15539: [PATCH] Setting user-emacs-directory François Févotte
[not found] ` <CAADsv96dEnf1aD+0=FvOHLPGXg2ARnL440Nya2ipQKRo648Dtw@mail.gmail.com>
2015-04-01 15:38 ` Oleh Krehel
2015-04-01 15:49 ` Drew Adams
2015-04-01 16:48 ` Oleh Krehel [this message]
2015-04-01 17:16 ` François Févotte
2015-04-01 21:03 ` Stefan Monnier
2015-04-02 8:12 ` François Févotte
2013-10-06 17:08 bug#15539: 24.3; setting user-emacs-directory at command line invocation Mike Carifio
2016-02-15 10:31 ` bug#15539: [PATCH] Setting user-emacs-directory Alexis
2016-02-15 14:15 ` Eli Zaretskii
2016-02-24 4:03 ` Lars Ingebrigtsen
2016-02-24 17:15 ` Eli Zaretskii
2016-02-25 5:48 ` Lars Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2008-07-21 6:59 bug#583: Use XDG basedir spec for configuration files? Fernando
2019-08-27 21:57 ` Paul Eggert
2019-08-28 16:11 ` Glenn Morris
2019-08-28 18:11 ` Paul Eggert
2019-08-29 2:14 ` Glenn Morris
2019-08-29 6:22 ` Paul Eggert
2019-08-29 18:30 ` Glenn Morris
2019-08-30 8:02 ` Paul Eggert
2019-08-30 16:18 ` Glenn Morris
2019-09-01 1:56 ` bug#15539: [PATCH] Setting user-emacs-directory Paul Eggert
2019-09-02 23:45 ` Glenn Morris
2019-09-03 6:29 ` Paul Eggert
2019-09-08 14:54 ` Mike Carifio
2020-08-13 11:06 ` Lars Ingebrigtsen
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=87d23npzez.fsf@gmail.com \
--to=ohwoeowho@gmail.com \
--cc=15539@debbugs.gnu.org \
--cc=francois.fevotte@ensta.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).