From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 22926@debbugs.gnu.org
Subject: bug#22926: 24.5; `shell-command', `shell-command-default-error-buffer'
Date: Mon, 7 Mar 2016 08:52:18 -0800 (PST) [thread overview]
Message-ID: <40e1f856-b7a9-4221-9443-a1fdc526837d@default> (raw)
In-Reply-To: <<834mciuty3.fsf@gnu.org>>
> The second one cannot be usefully made shorter (going from 72
> columns to 36 doesn't sound like a move for the best).
I disagree. A maximum limit is a maximum limit. And it can affect
operations and tools such as window/frame fitting.
A 36-column line is not a "disaster". Even a 2-column line is not
a disaster.
> And since we have a 72 column line, having a 74-column line in the
> same doc string doesn't sound like a disaster to me.
Etc., etc. And if 74 then why not 76? And if 76 then why not 78...
The lines should respect the maximum limit. Simple, clear. Helps
users both directly and indirectly (e.g. window/frame fitting).
And no, it is not a "disaster" if lines do not respect the rule.
But it is a bug - not all bugs are disasters.
next parent reply other threads:[~2016-03-07 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<97b7c9cf-83fc-4d10-8f2b-836132fcc5ca@default>
[not found] ` <<<83ziubv72j.fsf@gnu.org>
[not found] ` <<4e20bee2-3a48-44d1-8501-f19ccc660b0a@default>
[not found] ` <<834mciuty3.fsf@gnu.org>
2016-03-07 16:52 ` Drew Adams [this message]
[not found] <<97b7c9cf-83fc-4d10-8f2b-836132fcc5ca@default>
[not found] ` <<83ziubv72j.fsf@gnu.org>
2016-03-06 21:30 ` bug#22926: 24.5; `shell-command', `shell-command-default-error-buffer' Drew Adams
2016-03-07 16:35 ` Eli Zaretskii
2016-03-06 15:14 Drew Adams
2016-03-06 17:40 ` Eli Zaretskii
2016-04-30 22:55 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40e1f856-b7a9-4221-9443-a1fdc526837d@default \
--to=drew.adams@oracle.com \
--cc=22926@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.