From: Emanuel Berg <incal@dataswamp.org>
To: emacs-devel@gnu.org
Subject: Re: bytecomp: doc string wider than 80 spurious warnings are back
Date: Wed, 27 Sep 2023 22:16:17 +0200 [thread overview]
Message-ID: <87il7vid7y.fsf@dataswamp.org> (raw)
In-Reply-To: p91ttrf1jce.fsf@google.com
T.V Raman wrote:
> For docstring, since Emacs is the one that is going to
> display the docstring, I think code in the Help system
> should take care of formatting the docstring to match the
> size of the window, not rely on the developer to write the
> docstring to match a hard-coded width. The easiest thing for
> the help buffer to do might be to just turn on
> visual-line-mode, so yes, I think this warning is
> ill-adviced and noisy
But maybe that will break lines where not intended/indented?
Also 80 columns is some safe standard for virtual
terminals, right?
Try 'echo $COLUMNS', what do you get? I get 80 in the
Linux VTs, and 90 in xterm.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-09-27 20:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 23:11 bytecomp: doc string wider than 80 spurious warnings are back T.V Raman
2023-09-26 1:55 ` Stefan Kangas
2023-09-26 13:59 ` T.V Raman
2023-09-27 11:22 ` Stefan Kangas
2023-09-27 15:38 ` T.V Raman
2023-09-27 16:16 ` Emanuel Berg
2023-09-27 19:56 ` T.V Raman
2023-09-27 20:16 ` Emanuel Berg [this message]
2023-09-28 7:47 ` Stefan Kangas
2023-09-28 14:18 ` T.V Raman
2023-09-28 23:04 ` Michael Heerdegen
2023-09-29 2:20 ` T.V Raman
2023-09-29 13:52 ` Eli Zaretskii
2023-09-29 14:16 ` Stefan Kangas
2023-09-29 14:26 ` T.V Raman
2023-09-29 16:06 ` Emanuel Berg
2023-09-29 16:16 ` Eli Zaretskii
2023-09-28 7:38 ` Stefan Kangas
2023-09-28 14:16 ` T.V Raman
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=87il7vid7y.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=emacs-devel@gnu.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).