all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: p.stephani2@gmail.com, 24837@debbugs.gnu.org,
	21609@debbugs.gnu.org,
	bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org
Subject: bug#24837: bug#21609: bug#24837: 26.0.50; term.el: In char mode, displayed and executed commands can differ
Date: Tue, 10 Oct 2017 15:35:33 +0300	[thread overview]
Message-ID: <8360bnqiy2.fsf@gnu.org> (raw)
In-Reply-To: <bcb5151d-f72f-7f16-539a-b8d1d100e3d3@orcon.net.nz> (message from Phil Sainty on Wed, 11 Oct 2017 00:11:17 +1300)

> Cc: p.stephani2@gmail.com, 24837@debbugs.gnu.org, 21609@debbugs.gnu.org,
>  bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org
> From: Phil Sainty <psainty@orcon.net.nz>
> Date: Wed, 11 Oct 2017 00:11:17 +1300
> 
> On 10/10/17 04:32, Eli Zaretskii wrote:
> >> +*** New user options `term-char-mode-buffer-read-only' and
> >> +`term-char-mode-point-at-process-mark'
> 
> > I have a difficulty understanding why the user would like to change
> > the values of these options from their defaults.  How about revising
> > this text to describe (a) the default behavior, and (b) when would
> > someone want to change that by tweaking these options?
> 
> I'm likewise not sure whether users will *actually* want to do this.

In that case, the text should say something like

  Customize these options to nil if you want the previous behavior.

> In any case I'll see if I can improve the wording...

Thanks.





  reply	other threads:[~2017-10-10 12:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-31 14:10 bug#24837: 26.0.50; term.el: In char mode, displayed and executed commands can differ Philipp Stephani
2016-10-31 20:46 ` Phil Sainty
2016-11-23 19:44   ` Philipp Stephani
2016-11-23 20:08     ` bug#21609: " Phil Sainty
2016-11-23 20:21       ` Philipp Stephani
2017-09-02 14:14         ` Eli Zaretskii
2017-09-03  2:58           ` Phil Sainty
2017-09-03  3:09             ` bug#21609: " Phil Sainty
2017-09-04  9:55             ` Phil Sainty
2017-09-04 10:10               ` bug#24837: " Phil Sainty
2017-09-04 11:59                 ` bug#21609: " Phil Sainty
2017-09-24 10:59             ` Philipp Stephani
2017-09-25  0:48               ` bug#21609: " Phil Sainty
2017-09-25  3:09                 ` Phil Sainty
2017-09-29  8:37                   ` Eli Zaretskii
2017-10-08 12:39                     ` bug#21609: " Phil Sainty
2017-10-09 14:04                       ` Phil Sainty
2017-10-09 15:32                         ` Eli Zaretskii
2017-10-10 10:16                           ` bug#28777: Clarifying the temporary documentation update marks in etc/NEWS Phil Sainty
2017-10-10 12:25                             ` Eli Zaretskii
2017-10-10 11:11                           ` bug#24837: bug#21609: bug#24837: 26.0.50; term.el: In char mode, displayed and executed commands can differ Phil Sainty
2017-10-10 12:35                             ` Eli Zaretskii [this message]
2017-10-12 10:54                               ` Phil Sainty
2017-10-12 12:04                                 ` bug#21609: " Eli Zaretskii
2017-10-12 21:24                                   ` Documenting a preference for US English? Phil Sainty
2017-10-13  5:11                                     ` Marcin Borkowski
2017-10-13  5:48                                     ` Paul Eggert
2017-10-13  6:29                                     ` Thien-Thi Nguyen
2017-10-13  8:35                                     ` Eli Zaretskii
2017-10-21  8:20                                 ` bug#24837: bug#21609: bug#24837: 26.0.50; term.el: In char mode, displayed and executed commands can differ Eli Zaretskii

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=8360bnqiy2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21609@debbugs.gnu.org \
    --cc=24837@debbugs.gnu.org \
    --cc=bug-gnu-emacs-bounces+psainty=orcon.net.nz@gnu.org \
    --cc=p.stephani2@gmail.com \
    --cc=psainty@orcon.net.nz \
    /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.