From: Miles Bader <miles.bader@necel.com>
Cc: rogers-emacs@rgrjr.dyndns.org, nickrob@snap.net.nz,
Luc Teirlinck <teirllm@dms.auburn.edu>,
emacs-devel@gnu.org
Subject: Re: comint-insert-input on non-command lines: A trivial fix, a quibble, and a bug
Date: Tue, 09 May 2006 11:33:20 +0900 [thread overview]
Message-ID: <buoac9sx6z3.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <jwvlktczk3s.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 08 May 2006 10:08:58 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> (defun field-at-pos (pos)
>> "Return the field at position POS, taking stickiness etc into account"
>> (let ((raw-field (get-char-property (field-beginning pos) 'field)))
>> (if (eq raw-field 'boundary)
>> (get-char-property (1- (field-end pos)) 'field)
>> raw-field)))
>
> How does this work?
> I don't see where the stickiness is tested/used.
`field-beginning' (and field-end) use stickiness info.
> Maybe we should export get_pos_property (in editfns.c) to elisp?
Perhaps so; what would be called? `insertion-property'?
-Miles
--
.Numeric stability is probably not all that important when you're guessing.
next prev parent reply other threads:[~2006-05-09 2:33 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 20:05 comint-insert-input on non-command lines: A trivial fix, a quibble, and a bug Bob Rogers
2006-05-08 0:31 ` Nick Roberts
2006-05-08 3:16 ` Luc Teirlinck
2006-05-08 3:49 ` Luc Teirlinck
2006-05-08 4:49 ` Miles Bader
2006-05-08 14:08 ` Stefan Monnier
2006-05-09 2:33 ` Miles Bader [this message]
2006-05-08 4:08 ` Luc Teirlinck
2006-05-08 4:18 ` Nick Roberts
2006-05-09 1:55 ` Bob Rogers
2006-05-09 3:11 ` Nick Roberts
2006-05-10 3:01 ` Bob Rogers
2006-05-10 5:57 ` Nick Roberts
2006-05-09 3:01 ` Luc Teirlinck
2006-05-09 3:21 ` Nick Roberts
2006-05-09 3:59 ` Luc Teirlinck
2006-05-09 6:17 ` Nick Roberts
2006-05-09 14:58 ` Luc Teirlinck
2006-05-10 1:09 ` Nick Roberts
2006-05-10 1:13 ` Luc Teirlinck
2006-05-10 1:58 ` Miles Bader
2006-05-10 2:21 ` Nick Roberts
2006-05-10 2:32 ` Miles Bader
2006-05-10 3:50 ` Nick Roberts
2006-05-10 4:09 ` Miles Bader
2006-05-10 4:41 ` Luc Teirlinck
2006-05-10 5:29 ` Nick Roberts
2006-05-10 6:06 ` Luc Teirlinck
2006-05-10 6:27 ` Miles Bader
2006-05-10 21:38 ` comint-insert-input on non-command lines: Nick Roberts
2006-05-11 1:12 ` Luc Teirlinck
2006-05-11 1:33 ` Luc Teirlinck
2006-05-11 18:31 ` Richard Stallman
2006-05-11 20:29 ` Nick Roberts
2006-05-11 22:40 ` Luc Teirlinck
2006-05-14 23:29 ` Richard Stallman
2006-05-15 3:46 ` Luc Teirlinck
2006-05-15 20:37 ` Richard Stallman
2006-05-28 2:11 ` Luc Teirlinck
2006-05-28 3:48 ` Luc Teirlinck
2006-05-29 3:41 ` Nick Roberts
2006-05-29 3:58 ` Luc Teirlinck
2006-05-31 3:14 ` Luc Teirlinck
2006-05-31 3:24 ` Bob Rogers
2006-05-09 4:15 ` comint-insert-input on non-command lines: A trivial fix, a quibble, and a bug Luc Teirlinck
2006-05-10 5:19 ` Luc Teirlinck
2006-05-10 6:04 ` Nick Roberts
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=buoac9sx6z3.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=nickrob@snap.net.nz \
--cc=rogers-emacs@rgrjr.dyndns.org \
--cc=teirllm@dms.auburn.edu \
/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).