From: raman@google.com (T.V Raman)
To: bruce.connor.am@gmail.com
Cc: emacs-devel@gnu.org, raman@google.com
Subject: Re: Async Package.el Feedback
Date: Tue, 7 Apr 2015 10:32:19 -0700 [thread overview]
Message-ID: <21796.5283.460048.898286@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <CAAdUY-JVX1SkhtKXnTH+P9_45=u4ccCyBP+jCd5StnJCPwv1Kw@mail.gmail.com>
For now, the first solution sounds good to me -- personally
I've always found env vars a source of surprize and prefer to keep
emacs customizations inside emacs. What I do wish for (separate from
package.el) is the ability to
1. Have the custom file split into a per-package collection of files
and
2. A solution that encrypts them all.
The present giant custom file gets very fragile -- I keep losing
settings inexplicably, and encryption would be nice.
Artur Malabarba writes:
> I just did the following and I don't get any prompt.
>
> ln -s file1 file2
> emacs -q
> M-x find-file file2
>
> But if `file1' is a version controled file, then I do get the prompt
> (asRasmus explained).
>
> I think I'll do 2 things about this:
>
> 1. Read the contents of the file before visiting it, so if it already
> contains `package-initialize' we don't need to visit it at all. This
> will get rid of this prompt for users who version control their init
> file.
> 2. Do this visiting thing during package-initialize instead of during
> package-install, this way it should only happen once per session
> (unless the user manually initializes again, which is not a big
> issue). This way, if another unexpected corner case like this shows
> up, the user won't get faced with the problem 28 times in a row.
>
>
> Another possibility I've been considering would be to let go of this
> solution and switch to the second solution initially proposed on the
> other thread (checking a file or an enviroment variable to decide
> whether to package-initialize at startup or not).
>
> 2015-04-07 17:28 GMT+01:00 T.V Raman <raman@google.com>:
> > Simple way to repro: create symlink foo to file bar, then find-file
> > foo you'll see the dialog/prompt I'm talking about.
> > --
> >
> > --
--
--
next prev parent reply other threads:[~2015-04-07 17:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 0:29 Async Package.el Feedback raman
2015-04-07 9:41 ` Artur Malabarba
2015-04-07 15:23 ` raman
2015-04-07 16:08 ` Artur Malabarba
2015-04-07 16:28 ` T.V Raman
2015-04-07 17:22 ` Artur Malabarba
2015-04-07 17:32 ` T.V Raman [this message]
2015-04-07 17:46 ` Artur Malabarba
2015-04-07 16:20 ` Rasmus
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=21796.5283.460048.898286@retriever.mtv.corp.google.com \
--to=raman@google.com \
--cc=bruce.connor.am@gmail.com \
--cc=emacs-devel@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.
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.