unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: 20011@debbugs.gnu.org
Subject: bug#20011: etc/PROBLEMS: updates, wording, typos
Date: Fri, 06 Mar 2015 09:10:54 +0000	[thread overview]
Message-ID: <87sidize1t.fsf@violet.siamics.net> (raw)
In-Reply-To: <83ioeeo6rc.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 06 Mar 2015 10:43:51 +0200")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>>>>> From: Ivan Shmakov  Date: Thu, 05 Mar 2015 21:49:22 +0000

 >> Please consider the patch MIMEd.

 >> * etc/PROBLEMS: Use 'which' where appropriate (was: 'that'); mention
 >> visible-cursor; a few more mentions of ~/.Xresources and xrdb(1);
 >> refer to 'GNU Coreutils' and 'X Window' (were: 'GNU Fileutils' and
 >> 'X Windows', respectively); other similar fixes and updates.

 > There's nothing wrong with using "that" in these contexts,

	AIUI, there’s nothing wrong with using “which” there, either.

 > it's pretty standard English usage, and we use it all over the place
 > in the Emacs documentation.

	Personally, I find “that” sentences somewhat harder to read
	/in general./  I still hope someone with English skills better
	than mine could re-check these cases and apply the changes
	suggested where sensible.

 > So please submit a patch without those parts.

	ACK.

 > Also, "X Window" is incorrect; use "X Window system" or just "X"
 > instead.

	Indeed, I stand corrected.  (Though it’s X Window /S/ystem.)

 > This part:

 >>  Alternatively, if you want a blinking underscore as your Emacs cursor,
 >> -change the "cvvis" capability to send the "\E[?25h\E[?0c" command.
 >> +set the `visible-cursor' variable to nil in your ~/.emacs:
 >> +  (setq visible-cursor nil)

 > replaces a recipe with an entirely different one.  Why not keep both?

	The former recipe seems to predate the introduction of
	visible-cursor.  I see no reason to keep it now that there’s an
	easy way to solve the issue without having to modify terminfo or
	restart Emacs, etc.  I presume that the more experienced users
	will be able to gather all what necessary for a terminfo-based
	solution from the “use software cursor” recipe just above the
	one at hand.

-- 
FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A





  reply	other threads:[~2015-03-06  9:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 21:49 bug#20011: etc/PROBLEMS: updates, wording, typos Ivan Shmakov
2015-03-06  8:43 ` Eli Zaretskii
2015-03-06  9:10   ` Ivan Shmakov [this message]
2015-03-06 10:23     ` Eli Zaretskii
2015-04-04 20:20       ` Ivan Shmakov
2015-04-04 21:23         ` Eli Zaretskii
2015-04-07 17:47           ` Ivan Shmakov
2015-03-06 16:58     ` Glenn Morris
2015-04-04 20:25       ` Ivan Shmakov
2015-04-05  9:10         ` Richard Stallman

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=87sidize1t.fsf@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=20011@debbugs.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 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).