From: Bastien <bzg@altern.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Karl Fogel <kfogel@red-bean.com>,
Tassilo Horn <tassilo@member.fsf.org>,
Reiner Steib <reiner.steib@gmx.de>,
emacs-devel@gnu.org
Subject: Re: bookmark.el and lisp/gnus/gnus-bookmark.el
Date: Sat, 08 Mar 2008 20:47:42 +0000 [thread overview]
Message-ID: <87pru5gcy9.fsf@bzg.ath.cx> (raw)
In-Reply-To: <jwv3ar156yl.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 08 Mar 2008 14:54:17 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> If we get rid of the annotation argument for this single function, it
>> means the annotation has to be done before this function returns sth
>> that can be used as the suggested name for the bookmark.
>
> AFAICT getting rid of the annotation argument means nothing at all,
> other than that the annotation will have to be added by the generic
> bookmark-set code rather than being done by every single
> bookmark-make-record-function.
For now `bookmark-set' asks for an annotation (if required), sends it to
`bookmark-make' which calls `bookmark-make-record-function' with the
annotation as an argument.
IIUC Tassilo suggested that the annotation should be directly handled by
`bookmark-make-record-function', which seems correct to me. What you
propose is to handle annotation in `bookmark-set' (or preferrably in
`bookmark-make') -- this is _feasible_, but it looks weird to me since
the annotation is really part of the record.
BTW, I really think the name suggestion should be taken care of by
`bookmark-make-record-function' (with an optional "name" arg), not
by a separate call to `bookmark-make-name-function'...
Anyway - I let Karl summary and decide on this!
--
Bastien
next prev parent reply other threads:[~2008-03-08 20:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 18:06 bookmark.el and lisp/gnus/gnus-bookmark.el Karl Fogel
2008-03-06 18:45 ` Stefan Monnier
2008-03-06 19:51 ` Bastien
2008-03-06 20:29 ` Karl Fogel
2008-03-06 20:39 ` Bastien
2008-03-06 20:42 ` Karl Fogel
[not found] ` <87iqzz7xr8.fsf@member.fsf.org>
2008-03-07 17:05 ` Karl Fogel
2008-03-07 17:25 ` Bastien
2008-03-06 21:27 ` Stefan Monnier
2008-03-06 23:15 ` Bastien
2008-03-07 8:24 ` Tassilo Horn
2008-03-07 12:29 ` Bastien
2008-03-07 14:07 ` Tassilo Horn
2008-03-07 14:13 ` Bastien
2008-03-07 15:12 ` Tassilo Horn
2008-03-07 17:08 ` Karl Fogel
2008-03-07 17:20 ` Bastien
2008-03-07 17:34 ` Karl Fogel
2008-03-07 17:45 ` Bastien Guerry
2008-03-07 18:08 ` Karl Fogel
2008-03-07 18:19 ` Bastien
2008-03-07 19:34 ` Bastien Guerry
2008-03-07 21:51 ` Stefan Monnier
2008-03-07 22:40 ` Stefan Monnier
2008-03-08 1:31 ` Bastien
2008-03-08 2:38 ` Stefan Monnier
2008-03-08 2:43 ` Karl Fogel
2008-03-08 10:06 ` Bastien
2008-03-08 19:54 ` Stefan Monnier
2008-03-08 20:47 ` Bastien [this message]
2008-03-08 23:20 ` Stefan Monnier
2008-03-10 2:29 ` Karl Fogel
2008-03-08 11:35 ` Reiner Steib
2008-03-08 11:56 ` Bastien
2008-03-07 12:23 ` Bastien
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=87pru5gcy9.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--cc=monnier@iro.umontreal.ca \
--cc=reiner.steib@gmx.de \
--cc=tassilo@member.fsf.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).