From: Eli Zaretskii <eliz@gnu.org>
To: Max <maxim.suraev@campus.tu-berlin.de>
Cc: 15539@debbugs.gnu.org
Subject: bug#15539: comment
Date: Fri, 04 Nov 2016 09:28:50 +0200 [thread overview]
Message-ID: <83mvhfln4d.fsf@gnu.org> (raw)
In-Reply-To: <9c71f3ab-6322-c7fd-b98d-28f27d6c51f1@campus.tu-berlin.de> (message from Max on Thu, 3 Nov 2016 23:32:01 +0100)
> From: Max <maxim.suraev@campus.tu-berlin.de>
> Date: Thu, 3 Nov 2016 23:32:01 +0100
>
> As an Emacs user I would like to kindly request you to reconsider this bug.
>
> I think that the added complexity (look at the patch size, and even that is more
> comments than code) is more than justified by the convenience it adds.
The "complexity" mentioned in the discussion of this bug did not
allude to the size or complexity of the patch, it alluded to the
complexity this would add to Emacs and its development/maintenance:
where previously user-emacs-directory and the directory pointed to by
HOME in the environment were one and the same, now they will not be.
I think if we want to revisit this issue, we should come up with the
use cases where this feature would be useful, and see if they are
important enough to justify the price. AFAIR, no use cases were
provided with the original request.
Thanks.
next prev parent reply other threads:[~2016-11-04 7:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-06 17:08 bug#15539: 24.3; setting user-emacs-directory at command line invocation Mike Carifio
2015-03-13 15:01 ` bug#15539: Setting " François Févotte
2015-03-16 0:36 ` Glenn Morris
2015-03-16 7:28 ` François Févotte
2015-03-17 10:08 ` François Févotte
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
2016-11-03 22:32 ` bug#15539: comment Max
2016-11-04 7:28 ` Eli Zaretskii [this message]
2016-11-04 12:42 ` Evgeny Roubinchtein
2016-11-04 12:55 ` Noam Postavsky
2016-11-04 13:59 ` Eli Zaretskii
2016-12-14 18:43 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mvhfln4d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15539@debbugs.gnu.org \
--cc=maxim.suraev@campus.tu-berlin.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.