From: "Ilya N. Golubev" <gin@mo.msk.ru>
Cc: bug-gnu-emacs@gnu.org, Jerry James <james@xemacs.org>,
rms@gnu.org, xemacs-beta@xemacs.org
Subject: customizing inhibit-field-text-motion [Re: comint loses prompt boundary]
Date: Mon, 18 Dec 2006 18:56:31 +0300 [thread overview]
Message-ID: <25r6uxgpu8.fsf@mo.msk.ru> (raw)
In-Reply-To: 13lkpeawcu.fsf@mo.msk.ru
`inhibit-field-text-motion', however, is marked as user option in
xemacs. Was so since field (re-) implementation appeared in its
`xemacs-base' package on 2004/09/07 20:09:16 +0. This is perhaps why
assumed that is is also user option in emacs.
On Thu, 14 Dec 2006 00:39:52 +0900 Miles Bader wrote in
<87lklbu7nb.fsf@catnip.gol.com> about it in comint mode buffers:
> If you set it permanently, you are asking for trouble.
This should also hold for comint in xemacs, now that it is largely
synched with emacs. Maintainer(s) of fields in both in emacs and
xemacs, please clarify `inhibit-field-text-motion' status.
This does not necessarily mean stripping it of user option mark.
Setting it permanently to non-`nil' may certainly be useful as
described in other messages on the topic. This is the primary reason
why I personally favor making / leaving `inhibit-field-text-motion'
user option. This has nothing to do with compatibility with xemacs
implementation, which is even inconsistent in other ways as mentioned
in <13lkpeawcu.fsf@mo.msk.ru> of Thu, 24 Aug 2006 21:15:29 +0400
(<checking for fields>).
Note that `inhibit-field-text-motion' status issue is largely
independent of those described in <checking for fields>. Most of them
remain even if `inhibit-field-text-motion' becomes officially
customizeable. However, setting `inhibit-field-text-motion' is a way
around some of these issues.
prev parent reply other threads:[~2006-12-18 15:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 20:32 comint loses prompt boundary Ilya N. Golubev
2006-09-06 20:41 ` comint loses prompt boundary in cvs, too Ilya N. Golubev
[not found] ` <E1GLRDD-0000mS-2D@fencepost.gnu.org>
[not found] ` <59ejumjzz2.fsf@mo.msk.ru>
[not found] ` <E1GLjTm-0000cp-DO@fencepost.gnu.org>
[not found] ` <843bazvd1b.fsf@mo.msk.ru>
[not found] ` <comint_field_movement_fix@mo.msk.ru>
2006-12-12 18:07 ` shell completion documentation [Re: comint loses prompt boundary] Ilya N. Golubev
2006-12-12 18:08 ` field movement fix " Ilya N. Golubev
2006-12-15 16:11 ` field movement fix: `NEWS' change Ilya N. Golubev
2006-12-14 5:29 ` shell completion documentation [Re: comint loses prompt boundary] Richard Stallman
2006-12-14 17:51 ` shell completion documentation Ilya N. Golubev
2006-12-15 21:24 ` Richard Stallman
2006-12-15 23:48 ` bug reports vs manuals [Re: shell completion documentation] Ilya N. Golubev
2006-12-16 20:04 ` shell completion documentation Richard Stallman
2006-12-18 19:06 ` Ilya N. Golubev
2006-12-20 13:00 ` Richard Stallman
2006-12-20 20:59 ` what makes read it? [Re: shell completion documentation] Ilya N. Golubev
[not found] ` <mailman.1817.1166000505.2155.bug-gnu-emacs@gnu.org>
2006-12-13 15:39 ` shell completion documentation [Re: comint loses prompt boundary] Miles Bader
2006-12-13 18:07 ` Ilya N. Golubev
2006-12-14 3:49 ` Miles Bader
2006-12-15 23:48 ` comint loses prompt boundary Ilya N. Golubev
2006-08-24 17:15 ` checking for fields Ilya N. Golubev
2006-08-25 20:25 ` Richard Stallman
[not found] ` <02473b3c6f4154-gin@mo.msk.ru>
[not found] ` <02473b40868335-gin@mo.msk.ru>
2006-08-28 17:47 ` Ilya N. Golubev
2006-08-29 11:47 ` Richard Stallman
2006-08-29 20:30 ` pretest downloads [Re: checking for fields] Ilya N. Golubev
2006-08-30 17:58 ` Richard Stallman
2006-12-18 15:56 ` Ilya N. Golubev [this message]
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=25r6uxgpu8.fsf@mo.msk.ru \
--to=gin@mo.msk.ru \
--cc=bug-gnu-emacs@gnu.org \
--cc=james@xemacs.org \
--cc=rms@gnu.org \
--cc=xemacs-beta@xemacs.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).