From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 2291@debbugs.gnu.org
Subject: bug#2291: 23.0.90; finder-commentary
Date: Wed, 27 Apr 2016 11:05:16 -0700 (PDT) [thread overview]
Message-ID: <5497a333-6d80-4627-8b31-681a96659d6e@default> (raw)
In-Reply-To: <87fuu7exwq.fsf@gnus.org>
> >> Wouldn't it make more sense just to use the *Help* buffer? It has a
> >> nice history and stuff...
> >
> > No, certainly not. It should be commentary-specific, and file-specific,
> > as described in the bug report.
>
> It would be unusual. Most of these help-ish commands reuse the same
> buffer, and if you want to keep several of them around, you just rename
> the buffer yourself.
>
> So I don't think there's anything more to be done on this report.
This is nuts. `finder-commentary' is file-specific. Anyone
who uses it (and admittedly it is underused - most users know
nothing about its existence) uses it on multiple files.
You might have noticed recently a bunch of mails about having
multiple grep buffers etc. Well this is even more important
than that - and simpler, as this is just file-specific. Each
file should get its own finder-commentary buffer, named after it.
prev parent reply other threads:[~2016-04-27 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87iqmjokga.fsf@cyd.mit.edu>
2009-02-11 18:36 ` bug#2291: 23.0.90; finder-commentary Drew Adams
2009-02-11 23:35 ` Drew Adams
2009-02-13 15:19 ` Eli Zaretskii
2009-03-08 20:05 ` bug#2291: marked as done (23.0.90; finder-commentary) Emacs bug Tracking System
2016-04-27 17:43 ` bug#2291: 23.0.90; finder-commentary Lars Ingebrigtsen
2016-04-27 17:53 ` Drew Adams
2016-04-27 17:58 ` Lars Ingebrigtsen
2016-04-27 18:05 ` Drew Adams [this message]
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=5497a333-6d80-4627-8b31-681a96659d6e@default \
--to=drew.adams@oracle.com \
--cc=2291@debbugs.gnu.org \
--cc=larsi@gnus.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 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).