From: 路客 <luke.yx.lee@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: [elpa] master 74818d5: Brief Mode v5.86 release.
Date: Sun, 21 Oct 2018 11:40:02 +0800 [thread overview]
Message-ID: <CAA=xLRN7AUSRfEUq-ECrMXiwQJWx1W2tZBZjdofxF4rF3sdQrQ@mail.gmail.com> (raw)
In-Reply-To: <jwvefckqwvf.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 4176 bytes --]
> But that's also the "normal" package.el installation, so there's no need
> to search for brief.el: after the above command, Emacs will know where
> to find brief.el and `b` could just fire `emacs -f brief-mode` and be
> done with it.
Aside from the major purpose of 'b' for new users, there is a minor
purpose of 'b' -- a quick convenient shortcut for experienced users,
a pure & clean Emacs+Brief environment. Just like the "-q" or "-Q"
argument is for Emacs. You might notice by default I add "-q" in 'b'
and gave an "-nq" to reverse it. I would like 'b' to behave just like
"emacs -q" or "emacs -Q", but, with BriefMode as it's default keymap.
For myself, I from time to time need to launch a clean emacs env (to
bypass my lengthy .emacs init seq) for some quick editing, sometimes
emacsclient is just not adequate, therefore the "emacs -q" was
supposed to be good enough for that but just lack of the brief keymap.
Therefore with "-q" so I can't just fire it with "-f brief-mode" and
therefore it came along with the version/path things.
If you have a better way to launch Emacs with -q while being able to do
similar things like "-f brief-mode", *please definitively let me know*.
I myself don't like those default version things but I got no better
way. For a personal script I don't have that locally; but when it
extended for other users or new users, with Brief as an installed
Emacs package, I can't find a faster way to direct access
"~/.emacs.d/elpa/brief-XXX" without any searching. As I mentioned
in my earlier reply I can make things more complicated by things like
a 'find ~/.emacs.d/elpa -name b' but then I will need to sort
"by versions" if there are several versions returned (which involves
*version format* comparison like: v5.100 > v5.90). Of course, this
won't happen immediately as currently there is only v5.86. But once
there are more other versions installed it suppose to slow down things.
> That's also why I suggested introducing another function (like
> `brief-mode-full`) which would call brief plus setup those
> (h)scroll vars.
Yap, that's a good idea and I can get rid of those default settings
in 'b' altogether. I will do that in my next release.
Best regards,
Luke Lee
Stefan Monnier <monnier@iro.umontreal.ca> 於 2018年10月21日 週日 上午2:51寫道:
> >> 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...
>
> But that's also the "normal" package.el installation, so there's no need
> to search for brief.el: after the above command, Emacs will know where
> to find brief.el and `b` could just fire `emacs -f brief-mode` and be
> done with it.
>
> > 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.
>
> IIUC you found the answer in the mean time: the package header needed
> a `Package-Type: multi`.
>
> > Once users find the behavior of launching 'b' and of Emacs+briefpkg
> > differs, they will findout in the 'b' script. Surely better be in
> > README.org.
>
> That's also why I suggested introducing another function (like
> `brief-mode-full`) which would call brief plus setup those
> (h)scroll vars.
>
>
> Stefan
>
--
Best regards,
Luke Lee
[-- Attachment #2: Type: text/html, Size: 5236 bytes --]
next prev parent reply other threads:[~2018-10-21 3:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181018141131.22680.53035@vcs0.savannah.gnu.org>
[not found] ` <20181018141132.6E8BA208EC@vcs0.savannah.gnu.org>
2018-10-18 15:43 ` [elpa] master 74818d5: Brief Mode v5.86 release Stefan Monnier
2018-10-19 15:35 ` Stefan Monnier
2018-10-19 15:41 ` Stefan Monnier
2018-10-19 15:47 ` 路客
2018-10-19 16:47 ` Stefan Monnier
2018-10-20 16:01 ` 路客
2018-10-20 18:51 ` Stefan Monnier
2018-10-21 3:40 ` 路客 [this message]
2018-10-21 14:23 ` Stefan Monnier
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='CAA=xLRN7AUSRfEUq-ECrMXiwQJWx1W2tZBZjdofxF4rF3sdQrQ@mail.gmail.com' \
--to=luke.yx.lee@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).