From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: comint-insert-input on non-command lines: A trivial fix, a quibble, and a bug
Date: Wed, 10 May 2006 14:21:16 +1200 [thread overview]
Message-ID: <17505.19996.720964.47189@farnswood.snap.net.nz> (raw)
In-Reply-To: <buopsimfxoo.fsf@dhapc248.dev.necel.com>
> > I've installed a patch which includes Miles's. I called his new function
> > field-at-point rather than ield-at-pos for consistency with names like
> > posn-at-point and to avoid confusion with the more general meaning of
> > position.
>
> Please don't rename my functions without asking first. I've restored
> the proper name.
>
> [The function doesn't refer to point at all...]
Yes, you're right, posn-at-point should really be posn-at-pos. You could
improve field-at-pos further by making the argument pos optional and defaulting
to point. I won't do that because I can't be bothered to ask if its OK
to change `your' functions first although I assume we can all use them
without asking.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-05-10 2:21 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17505.19996.720964.47189@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@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.