From: Mark Oteiza <mvoteiza@udel.edu>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Jeff Clough <kb1vqh@gmail.com>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: master cd0a795: Output number of characters added to file (Bug#354)
Date: Fri, 7 Apr 2017 20:17:56 -0400 [thread overview]
Message-ID: <20170408001756.fqpbya5de2w5bfpt@holos.localdomain> (raw)
In-Reply-To: <CAM-tV-_H8W4nayZgp_XQqG=oWE0eusXqwQnyBB1x1-RzN5QaiA@mail.gmail.com>
On 07/04/17 at 08:06am, Noam Postavsky wrote:
> On Thu, Apr 6, 2017 at 11:30 PM, Mark Oteiza <mvoteiza@udel.edu> wrote:
> >>
> >> Output number of characters added to file (Bug#354)
> >
> > This behavior is unnecessarily verbose, at least when just interactively
> > saving buffers. Haven't tested this otherwise. If I cared about the
> > number of characters in the buffer I'd look in the mode line or just do
> > C-x =.
>
> Would it help if we rearranged the message so that the number of
> characters go at the end? Something like:
>
> Wrote /foo/bar/blah (1314 characters)
I still don't understand the purpose of this change, as I've never been
troubled by not knowing the number of characters written, and the original
report didn't outline a recipe. So, I'm not sure I can really comment
other than suggesting a revert.
next prev parent reply other threads:[~2017-04-08 0:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170407022529.14820.30445@vcs0.savannah.gnu.org>
[not found] ` <20170407022531.17D812084C@vcs0.savannah.gnu.org>
2017-04-07 3:30 ` master cd0a795: Output number of characters added to file (Bug#354) Mark Oteiza
2017-04-07 7:14 ` Eli Zaretskii
2017-04-07 22:50 ` Paul Eggert
2017-04-07 23:02 ` Kaushal Modi
2017-04-08 0:13 ` Noam Postavsky
2017-04-08 0:16 ` Mark Oteiza
2017-04-07 12:06 ` Noam Postavsky
2017-04-08 0:17 ` Mark Oteiza [this message]
2017-04-08 7:34 ` Eli Zaretskii
2017-04-08 14:08 ` Mark Oteiza
2017-04-09 20:03 ` Mark Oteiza
2017-04-07 13:42 ` Michael Albinus
2017-04-07 22:27 ` Noam Postavsky
2017-04-07 16:48 ` Glenn Morris
2017-04-07 21:41 ` Glenn Morris
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=20170408001756.fqpbya5de2w5bfpt@holos.localdomain \
--to=mvoteiza@udel.edu \
--cc=emacs-devel@gnu.org \
--cc=kb1vqh@gmail.com \
--cc=npostavs@gmail.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).