From: Tak Ota <Takaaki.Ota@am.sony.com>
To: <stephen@xemacs.org>
Cc: andreas.roehler@online.de, emacs-devel@gnu.org
Subject: Re: simple useful functions
Date: Wed, 3 Nov 2010 11:08:45 -0700 [thread overview]
Message-ID: <20101103.110845.494787500.Takaaki.Ota@am.sony.com> (raw)
In-Reply-To: <87tyjyiujz.fsf@uwakimon.sk.tsukuba.ac.jp>
Wed, 3 Nov 2010 03:13:36 -0700: "Stephen J. Turnbull" <stephen@xemacs.org> wrote:
> Andreas Röhler writes:
>
> > AFAIU `occur' selects lines, not strings.
>
> Sure, but the words "occur" and "occurance" don't imply
> line-oriented. IOW, that's an implementation detail AFAICS.
>
> You can argue this functionality doesn't belong in occur, but I don't
> think its current line-oriented implementation is a reason not to add
> it there. More to the point would be that `collect-string' might be
> most useful in Lisp programs, but `occur' is interactive. There may
> be other reasons, too. Note that the interactive vs. programmatic
> issue might very well be a problem with my clumsy implementation --
> that was just a proof of concept.
Try M-x collect-string. It is interactive. And recently in regard to
my work I most frequently use collect-string to extract specific URLs
from XML and HTML files. I rarely use it in Lisp programming.
> Even so, I think it belongs in the "occur-" namespace. I think it's
> most discoverable there.
>
> > Isn't `collect-string' an instructive example how to write simple and
> > effective code in Emacs Lisp?
>
> "Instructive examples" belong in the Elisp tutorial, not in the core
> code.
>
> The questions about `collect-string' should be, "Does this
> *functionality* belong in the core codebase? If so, where?"
This logic makes sense.
-Tak
next prev parent reply other threads:[~2010-11-03 18:08 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 18:56 simple useful functions Tak Ota
2010-10-29 3:39 ` Stephen J. Turnbull
2010-10-29 18:13 ` Tak Ota
2010-10-29 19:02 ` Drew Adams
2010-10-29 19:26 ` Andreas Schwab
2010-10-29 20:19 ` Drew Adams
2010-10-29 20:47 ` Andreas Schwab
2010-10-29 20:56 ` Chad Brown
2010-10-29 21:23 ` Drew Adams
2010-10-30 9:01 ` Stephen J. Turnbull
2010-10-30 10:55 ` Thierry Volpiatto
2010-11-02 0:40 ` Tak Ota
2010-11-02 2:22 ` Stephen J. Turnbull
2010-11-03 0:38 ` Tak Ota
2010-11-03 5:27 ` Stephen J. Turnbull
2010-11-03 8:09 ` Andreas Röhler
2010-11-03 10:13 ` Stephen J. Turnbull
2010-11-03 18:08 ` Tak Ota [this message]
2010-11-03 18:01 ` Tak Ota
2010-11-04 2:10 ` Stephen J. Turnbull
2010-11-04 2:20 ` Tak Ota
2010-11-04 13:58 ` collect-string (was: simple useful functions) Stefan Monnier
2010-11-04 18:36 ` Tak Ota
2010-11-04 20:18 ` Tak Ota
2010-11-04 20:27 ` Tak Ota
2010-11-05 7:52 ` Andreas Röhler
2010-11-08 18:36 ` collect-string Stefan Monnier
2010-11-09 0:18 ` collect-string Tak Ota
2010-11-09 9:06 ` collect-string Stephen J. Turnbull
2010-11-10 2:12 ` collect-string Tak Ota
2010-11-30 2:14 ` collect-string Tak Ota
2010-11-30 5:27 ` collect-string Stephen J. Turnbull
2010-12-02 1:59 ` collect-string Tak Ota
2010-12-02 7:00 ` collect-string Stephen J. Turnbull
2010-12-02 14:16 ` collect-string Stefan Monnier
2010-12-03 1:03 ` collect-string Tak Ota
2010-12-03 19:17 ` collect-string Stefan Monnier
2010-12-03 22:31 ` collect-string Tak Ota
2010-12-03 22:40 ` collect-string Davis Herring
2010-12-03 22:47 ` collect-string Tak Ota
2010-12-03 22:56 ` collect-string Stefan Monnier
2010-12-03 23:15 ` collect-string Tak Ota
2010-12-04 2:01 ` collect-string Stefan Monnier
2010-12-04 2:07 ` collect-string Tak Ota
2010-12-04 3:27 ` collect-string Glenn Morris
2010-10-29 8:44 ` simple useful functions Andreas Schwab
2010-11-02 7:27 ` Andreas Röhler
2010-12-03 23:37 ` Tak Ota
2010-12-04 2:36 ` Stefan Monnier
2010-12-04 2:58 ` Tak Ota
2010-12-04 4:36 ` Stefan Monnier
2010-12-04 9:10 ` David Kastrup
2010-12-06 14:08 ` René Kyllingstad
2010-12-06 19:31 ` Stefan Monnier
2010-12-06 18:39 ` Tak Ota
2010-12-06 20:23 ` Stefan Monnier
2010-12-06 21:25 ` Tak Ota
2010-12-07 3:24 ` Stefan Monnier
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=20101103.110845.494787500.Takaaki.Ota@am.sony.com \
--to=takaaki.ota@am.sony.com \
--cc=andreas.roehler@online.de \
--cc=emacs-devel@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 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.