From: Miles Bader <miles.bader@necel.com>
To: "Lennart Borgman \(gmail\)" <lennart.borgman@gmail.com>
Cc: Andreas@necel.com, "Stephen J. Turnbull" <stephen@xemacs.org>,
Röhler <andreas.roehler@online.de>,
emacs-devel@gnu.org
Subject: Re: mark-word
Date: Thu, 15 Nov 2007 18:18:44 +0900 [thread overview]
Message-ID: <buoejerg93f.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <473C05E4.6060106@gmail.com> (Lennart Borgman's message of "Thu\, 15 Nov 2007 09\:40\:04 +0100")
"Lennart Borgman (gmail)" <lennart.borgman@gmail.com> writes:
>> It could also be implemented rather simply using primitive functions.
>> The thing-at-point code is hairy and ugly, so it seems backwards to base
>> other simpler functions on it...
>
> Using thing-at-point to make mark-thing-at-point (and then
> mark-work-at-point etc) would mean that it is consistent and eaiser for
> the user to remember.
Why? The user doesn't care how mark-word-at-point (incidentally, this
is a crap name) is implemented.
-Miles
--
Love is a snowmobile racing across the tundra. Suddenly it flips over,
pinning you underneath. At night the ice weasels come. --Nietzsche
next prev parent reply other threads:[~2007-11-15 9:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 7:35 mark-word Andreas Röhler
2007-11-14 8:11 ` mark-word Stephen J. Turnbull
2007-11-14 8:26 ` mark-word David Kastrup
2007-11-14 11:27 ` mark-word Andreas Röhler
2007-11-14 17:24 ` mark-word Stephen J. Turnbull
2007-11-14 19:07 ` mark-word Lennart Borgman (gmail)
2007-11-15 0:33 ` mark-word Miles Bader
2007-11-15 8:40 ` mark-word Lennart Borgman (gmail)
2007-11-15 9:18 ` Miles Bader [this message]
2007-11-15 13:52 ` mark-word Lennart Borgman (gmail)
2007-11-15 10:04 ` mark-word Andreas Röhler
2007-11-14 17:02 ` mark-word Stephen J. Turnbull
2007-11-14 8:37 ` mark-word Leo
2007-11-14 16:35 ` mark-word Stephen J. Turnbull
2007-11-15 3:07 ` mark-word 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=buoejerg93f.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--cc=Andreas@necel.com \
--cc=andreas.roehler@online.de \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=miles@gnu.org \
--cc=stephen@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).