all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Drew Adams <drew.adams@oracle.com>
Cc: 26299@debbugs.gnu.org
Subject: bug#26299: 24.5; Use of `…' in Info
Date: Wed, 29 Mar 2017 23:40:43 -0400	[thread overview]
Message-ID: <877f373004.fsf@users.sourceforge.net> (raw)
In-Reply-To: <70f7b182-ca55-499c-8afe-6bd4aef370a1@default> (Drew Adams's message of "Wed, 29 Mar 2017 07:44:23 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> As one user, I find the adoption of `…' instead of `...' to be a
> retrogression, not an improvement.  It is far less readable.  Just one
> opinion.
>
> Compare, as one example among zillions:
>
>  -- Macro: with-help-window buffer-name body…
>
> with
>
>  -- Macro: with-help-window buffer-name body...
>
> I cannot imagine what someone thought, when making this change.  Did it
> come just because we _can_ now use that Unicode character?  That's not
> a reason that we _should_ use it in such contexts.

This seems to be another feature of the new (i.e., 5+) texinfo (like the
curly quotes).  I'm still using 4.13 so I see "..." here.  You can make
Emacs display "…" as "..." with

    (aset (or standard-display-table
              (setq standard-display-table (make-display-table)))
          ?… (vconcat "..."))






  reply	other threads:[~2017-03-30  3:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 14:44 bug#26299: 24.5; Use of `…' in Info Drew Adams
2017-03-30  3:40 ` npostavs [this message]
2017-03-30 13:49   ` Drew Adams
2017-03-30 14:34     ` Noam Postavsky
2017-03-30 14:56       ` Drew Adams
2017-06-12  2:49         ` Drew Adams
2017-06-12 14:24           ` Eli Zaretskii
2017-06-12 14:52             ` Drew Adams
2017-06-12 15:09               ` Eli Zaretskii
2017-06-12 15:18                 ` Drew Adams
2017-06-12 16:56                   ` Eli Zaretskii
2017-06-12 17:13                     ` Drew Adams
2019-09-29  3:21 ` Stefan Kangas

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=877f373004.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=26299@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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.