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: jrw@pobox.com, 28790@debbugs.gnu.org
Subject: bug#28790: [PATCH] Replaced "which see" with "q.v.".
Date: Sun, 15 Oct 2017 05:36:09 +0300	[thread overview]
Message-ID: <83y3odgmsm.fsf@gnu.org> (raw)
In-Reply-To: <c9d15ppent.fsf@fencepost.gnu.org> (message from Glenn Morris on Sat, 14 Oct 2017 18:07:02 -0400)

> From: Glenn Morris <rgm@gnu.org>
> Cc: John Williams <jrw@pobox.com>,  28790@debbugs.gnu.org
> Date: Sat, 14 Oct 2017 18:07:02 -0400
> 
> Eli Zaretskii wrote:
> 
> > The absolute majority of your proposed changes are in the doc strings,
> > where we already have a direct link to the documentation of a symbol
> > whose name precedes "which see".  So whether the reader understands
> > that or doesn't, the link is already there to click on, and no harm is
> > done by a relatively rare use of this phrase.
> 
> IMO there is no benefit either, as you explain above. "which see" is an
> anachronism in the age of hyperlinks. Is there any logic to where these
> "rare uses" appear - why do some links get them and most not? If there's
> no logic and no benefit, they should be removed as unnecessary verbiage.

In my book, if there's no benefit and no harm, the text should stay as
it is.





  parent reply	other threads:[~2017-10-15  2:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 21:22 bug#28790: [PATCH] Replaced "which see" with "q.v." John Williams
2017-10-12  1:44 ` Nick Helm
2017-10-12  3:51   ` Drew Adams
2017-10-12  6:48 ` Eli Zaretskii
2017-10-14 22:07   ` Glenn Morris
2017-10-14 22:52     ` John Williams
2017-10-15  2:36       ` Eli Zaretskii
2017-10-15  0:19     ` João Távora
2017-10-15  1:03       ` John Williams
2017-10-15 15:31         ` Drew Adams
2017-10-16  1:55           ` Richard Stallman
2017-10-16 21:47         ` Alan Third
2017-10-15  2:36     ` Eli Zaretskii [this message]
2017-10-13  0:26 ` bug#28790: " Richard Stallman
2017-10-13 18:34   ` John Williams
2017-10-13 18:55     ` Eli Zaretskii
2019-06-24 15:39   ` 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=83y3odgmsm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28790@debbugs.gnu.org \
    --cc=jrw@pobox.com \
    --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.