From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] ChangeLog width 74 -> 80
Date: Tue, 18 Jun 2013 15:47:00 -0000 [thread overview]
Message-ID: <51C07FCC.6090706@redhat.com> (raw)
In-Reply-To: <20130618153005.GA26742@host2.jankratochvil.net>
On 06/18/2013 04:30 PM, Jan Kratochvil wrote:
> On Tue, 18 Jun 2013 17:24:04 +0200, Pedro Alves wrote:
>> 74 is the default column width in emacs' changelog mode,
>> so it seems the explicit setting is just trying to making
>> sure everyone (that uses emacs) is using the default width,
>> even if one has it overridden in their .emacs file.
>
> That depends whether GDB still should workaround Emacs bugs or if GDB can be
> fixed for modern editors.
No reason to attach a straw man. If you want to argue for
80 columns, please do so without. I was merely stating facts,
and linking them into what I believe is the rationale for the
existing explicit setting. That is, the setting in the file overrides
a different default width a user may have configured in his emacs,
therefore, the setting in the ChangeLog file makes the width
consistent for emacs users).
Nobody said anything about bugs. Nor is emacs a non-modern editor.
As I said, I really don't care that much about the precise width.
It'd be nice to have it changed consistently across the tree
though.
--
Pedro Alves
next prev parent reply other threads:[~2013-06-18 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 15:09 Jan Kratochvil
2013-06-18 15:30 ` Pedro Alves
2013-06-18 15:34 ` Jan Kratochvil
2013-06-18 15:47 ` Pedro Alves [this message]
2013-06-18 15:51 ` Jan Kratochvil
2013-06-18 16:22 ` Pedro Alves
2013-06-18 18:02 ` Jan Kratochvil
2013-06-18 21:35 ` Joel Brobecker
2013-06-19 13:25 ` [cancel] " Jan Kratochvil
2013-06-19 7:50 ` Yao Qi
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=51C07FCC.6090706@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox