From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Test Alternative initialize scheme
Date: Sun, 8 Apr 2018 15:31:05 +0300 [thread overview]
Message-ID: <45899d0c-3cb0-5cbb-9fff-69cbd21c48da@gmail.com> (raw)
In-Reply-To: <86woxi8oco.fsf@zoho.com>
Most of those kits are .el file based, usually they provide a preset
~/.emacs.d. Actually since having multiple configurations like this is
somewhat common, maybe someone should open a feature request to
implement it as a flag out of box, something like
--with-user-emacs-directory...
It's less complicated for the end user, especially the new user, because
successfully configuring Emacs for different advanced applications
involves making dozens of decisions. Most of those decisions require
some knowledge and testing. And you may still wound up with something
controversial. This is even harder for a new user when there's already a
learning curve.
> why not put the
> same effort into making the software lay onto
> each other in a straightforward way bottom-up?
Because this requires each package developer to be aware of pretty much
every package that may be used simultaneously with yours. I'm explicitly
talking about Emacs here, since it's less of a problem in Unix world.
The way to help with it upstream is providing protocols for package devs
to use, the new xref is one such thing.
--
Best Regards,
Nikolay Kudryavtsev
next prev parent reply other threads:[~2018-04-08 12:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 23:12 Test Alternative initialize scheme Tim Johnson
2018-04-05 21:43 ` Nikolay Kudryavtsev
2018-04-05 21:57 ` Tim Johnson
2018-04-08 0:27 ` [solved]Test " Tim Johnson
[not found] ` <mailman.11759.1522964625.27995.help-gnu-emacs@gnu.org>
2018-04-06 19:06 ` Test " Emanuel Berg
2018-04-06 21:15 ` Nikolay Kudryavtsev
2018-04-07 6:41 ` Eli Zaretskii
2018-04-07 12:38 ` Nikolay Kudryavtsev
2018-04-07 12:53 ` Eli Zaretskii
[not found] ` <mailman.11799.1523049339.27995.help-gnu-emacs@gnu.org>
2018-04-06 21:55 ` Emanuel Berg
2018-04-07 12:20 ` Nikolay Kudryavtsev
2018-04-08 1:43 ` Emanuel Berg
2018-04-08 12:31 ` Nikolay Kudryavtsev [this message]
[not found] ` <mailman.11861.1523190672.27995.help-gnu-emacs@gnu.org>
2018-04-08 14:48 ` Emanuel Berg
2018-04-09 17:42 ` Nikolay Kudryavtsev
[not found] ` <mailman.11937.1523295742.27995.help-gnu-emacs@gnu.org>
2018-04-09 18:56 ` Emanuel Berg
2018-04-09 22:24 ` Nikolay Kudryavtsev
[not found] ` <mailman.11951.1523312688.27995.help-gnu-emacs@gnu.org>
2018-04-09 22:44 ` Emanuel Berg
2018-04-09 23:15 ` Nikolay Kudryavtsev
[not found] ` <mailman.11953.1523315732.27995.help-gnu-emacs@gnu.org>
2018-04-09 23:41 ` Emanuel Berg
[not found] <mailman.11717.1522883541.27995.help-gnu-emacs@gnu.org>
2018-04-05 0:34 ` Emanuel Berg
2018-04-05 0:55 ` Tim Johnson
2018-04-05 1:09 ` Emanuel Berg
[not found] ` <mailman.11718.1522889734.27995.help-gnu-emacs@gnu.org>
2018-04-05 1:15 ` Emanuel Berg
2018-04-05 1:28 ` Emanuel Berg
2018-04-05 15:15 ` Tim Johnson
2018-04-05 21:46 ` Tim Johnson
[not found] ` <mailman.11760.1522964821.27995.help-gnu-emacs@gnu.org>
2018-04-06 18:57 ` Emanuel Berg
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=45899d0c-3cb0-5cbb-9fff-69cbd21c48da@gmail.com \
--to=nikolay.kudryavtsev@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).