From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 10600@debbugs.gnu.org, Chong Yidong <cyd@gnu.org>
Subject: bug#10600: 24.0.92; `describe-char': text properties and [Show]
Date: Fri, 27 Jan 2012 21:28:48 +0100 [thread overview]
Message-ID: <CAAeL0SQGikLeYU8fKqAcO_8HD7mDOP2dc4tCd2kdV-z3_8VsoQ@mail.gmail.com> (raw)
In-Reply-To: <D75903FCCBB949B39DCEE21FB86B2C73@us.oracle.com>
On Fri, Jan 27, 2012 at 17:15, Drew Adams <drew.adams@oracle.com> wrote:
> The current window for that calculation does not correspond to *Help* at all.
> It is wrong to assume that *Help* will be displayed in a window having the same
> width as the window where the help command is invoked.
Yes.
> It's simply misguided to base the assumed *Help* window width on the width of
> any existing window.
I disagree. I think it makes sense to base it on the width of the
window used to display it. In cases like this one, it should be
possible to display the (empty) buffer, then generate its output.
> We already go to the trouble of
> wrapping help text at such a limit.
By hand, you mean? Because if you define a function with a docstring
100 chars long, and do M-x describe-function my-test-func <RET>,
there's no wrap at all.
Juanma
next prev parent reply other threads:[~2012-01-27 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 17:29 bug#10600: 24.0.92; `describe-char': text properties and [Show] Drew Adams
2012-01-27 7:31 ` Chong Yidong
2012-01-27 16:15 ` Drew Adams
2012-01-27 20:28 ` Juanma Barranquero [this message]
2012-01-27 21:43 ` Drew Adams
2012-01-28 17:15 ` Juanma Barranquero
2012-01-29 5:04 ` Drew Adams
2012-02-02 7:01 ` Kevin Rodgers
2012-02-02 11:08 ` 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=CAAeL0SQGikLeYU8fKqAcO_8HD7mDOP2dc4tCd2kdV-z3_8VsoQ@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=10600@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=drew.adams@oracle.com \
/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).