> Not sure what you mean exactly, here: `b` is a script that's part of the
> `brief` GNU ELPA package. So to get this script, they've had to
> "install" (at the very least download and unpack) that package already.
> The easiest way to install it is with `M-x package-install RET`, AFAIK
In EmacsWiki page (or "README.org") I suggest this command line:
$ emacs -Q -eval "(progn (package-initialize) (package-refresh-contents) \
(package-install 'brief) (save-buffers-kill-emacs))"
so basically a new user only need to copy&paste this command...
> (regarding other discussions about 'b'...)
However I am facing another more basic problem that I can't make
either 'b' or 'README.org' packed into brief package. I read thru all
the multi-file related info but they seems only applies to .el files.
I am still trying, if I still can't even pack 'b' or README.org I will just
put them in github and modify EmacsWiki and README.org about the above
command line without even using package. Of course the 'b' would need
to be modified accordingly.
> > Yes, quite a few bash specific things.
> I find it difficult to find those, but I usually find it easy to change
> the code not to use them, so if you can point them out I can try and
> see if I can remove this dependency without making the code worse.
Mainly about the array things. I would like to get rid of the
possibility that white space exists in some argument (like file name
or directory with white space) so bash arrays are more convenient to
me. There must be 'sh' ways to achieve this but maybe later when
I have time. Maybe 'b' need to be revised for github anyway.
> Are they likely to dig into the code of `b` to find that? Or look for
> a b.el file in the package (e.g. if they installed it via package.el
> they may not even know where to look to find b.el)?
> Maybe you could advertise those in a different way, e.g. in the README,
Once users find the behavior of launching 'b' and of Emacs+briefpkg
differs, they will findout in the 'b' script. Surely better be in
> I don't follow: the above definition already defines the
> `brief-auto-backup-mode` command which toggles.
Arg, you're right, will do that later.