all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: mvoteiza@udel.edu, larsi@gnus.org, 26796@debbugs.gnu.org,
	npostavs@users.sourceforge.net
Subject: bug#26796: 26.0.50; (2 characters) is usually wrong
Date: Mon, 08 May 2017 19:07:56 +0300	[thread overview]
Message-ID: <83d1bjcowz.fsf@gnu.org> (raw)
In-Reply-To: <x58tm7e3uv.fsf@fencepost.gnu.org> (message from Glenn Morris on Mon, 08 May 2017 11:59:52 -0400)

> From: Glenn Morris <rgm@gnu.org>
> Cc: Mark Oteiza <mvoteiza@udel.edu>,  larsi@gnus.org,  26796@debbugs.gnu.org,  npostavs@users.sourceforge.net
> Date: Mon, 08 May 2017 11:59:52 -0400
> 
> Eli Zaretskii wrote:
> 
> >> Was there any reason to implement it in the first place?
> >
> > Seems we are back at the discussion we had starting here:
> >
> >   http://lists.gnu.org/archive/html/emacs-devel/2017-04/msg00219.html
> 
> In which, if I read right, literally no-one was in favour of the feature?
> A feature that several people have now spent time debugging, tweaking,
> and documenting, and which will have to be supported going forwards.

Is this a complaint about something I did?  Just wondering.





  reply	other threads:[~2017-05-08 16:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-06  9:49 bug#26796: 26.0.50; (2 characters) is usually wrong Lars Ingebrigtsen
2017-05-06 10:32 ` Eli Zaretskii
2017-05-06 10:38   ` Lars Ingebrigtsen
2017-05-06 10:45   ` Lars Ingebrigtsen
2017-05-06 11:06     ` Eli Zaretskii
2017-05-06 12:16 ` npostavs
2017-05-06 14:19   ` Eli Zaretskii
2017-05-06 17:21     ` npostavs
2017-05-08  5:02     ` Mark Oteiza
2017-05-08 14:33       ` Eli Zaretskii
2017-05-08 15:59         ` Glenn Morris
2017-05-08 16:07           ` Eli Zaretskii [this message]
2017-05-09  0:41             ` Mark Oteiza
2017-05-09  4:39           ` npostavs
2017-05-07  1:11 ` Paul Eggert

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=83d1bjcowz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=26796@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mvoteiza@udel.edu \
    --cc=npostavs@users.sourceforge.net \
    --cc=rgm@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.