Re: Async Package.el Feedback

[T.V Raman]

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 <address@hidden>:
 > > Simple way to repro: create symlink foo to file bar, then find-file
 > > foo you'll see the dialog/prompt I'm talking about.
 > > --
 > >
 > > --

-- 

--