From: Kelly Dean <kellydeanch@yahoo.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 13146@debbugs.gnu.org
Subject: bug#13146: [PATCH] help-for-help interferes with buffer order, and displays help in too many windows
Date: Thu, 13 Dec 2012 00:12:13 -0800 (PST) [thread overview]
Message-ID: <1355386333.19763.YahooMailClassic@web141106.mail.bf1.yahoo.com> (raw)
In-Reply-To: <50C8517D.6060905@gmx.at>
> Does anyone see
> a downside to
> renaming the buffer used by `help-for-help' to
> *help-for-help* (with a
> leading space)?
That sounds like a good solution.
next prev parent reply other threads:[~2012-12-13 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 18:57 bug#13146: [PATCH] help-for-help interferes with buffer order, and displays help in too many windows Kelly Dean
2012-12-12 9:42 ` martin rudalics
2012-12-13 8:12 ` Kelly Dean [this message]
2012-12-14 10:24 ` martin rudalics
2012-12-16 11:58 ` Kelly Dean
2012-12-17 13:38 ` martin rudalics
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=1355386333.19763.YahooMailClassic@web141106.mail.bf1.yahoo.com \
--to=kellydeanch@yahoo.com \
--cc=13146@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).