unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: Bastien <bzg@altern.org>
Cc: Karl Fogel <kfogel@red-bean.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Reiner Steib <reiner.steib@gmx.de>,
	emacs-devel@gnu.org
Subject: Re: bookmark.el and lisp/gnus/gnus-bookmark.el
Date: Fri, 07 Mar 2008 15:07:24 +0100	[thread overview]
Message-ID: <87abla8w6b.fsf@member.fsf.org> (raw)
In-Reply-To: <87hcfi3egg.fsf@bzg.ath.cx> (Bastien's message of "Fri, 07 Mar 2008 12:29:03 +0000")

Bastien <bzg@altern.org> writes:

>>> This boils down to this: having a `bookmark-make-name-function'
>>> doing for the names of the bookmarks what
>>> `bookmark-make-cell-function' does for the records.  This would be
>>> locally set depending on the mode we're in.
>>>
>>> For now the the name of the bookmark is set by
>>> bookmark-buffer-file-name which doesn't return anything unless you
>>> are in a buffer visiting a file or an Info node, or dired.
>>
>> Hm, looking at the code `bookmark-buffer-file-name' is only called
>> for buffers that don't have `bookmark-make-record-function' set
>> locally, so I don't see why you would need that?
>
> I think you mean: `bookmark-make-cell-function', right?

Nope, Karl has renamed it to bookmark-make-record-function.

> Karl added this after I wrote the text you quote above.
>
>> Or am I late again and Karl's and Stefan's changes already do care oy
>> everything we need?
>
> Yes, they do!

Good boys! ;-)

> Now a mode can define `bookmark-make-cell-function' so that it tells
> bookmark.el how to set the name of the bookmark.

Now it's bookmark-make-record-function, but that has been there (as
b-m-cell-f) for a while now...

,----[ ~/repos/emacs/lisp/ChangeLog ]
| 2007-12-26  Tassilo Horn  <tassilo@member.fsf.org>
| 
| 	* image-mode.el (image-bookmark-make-cell, image-bookmark-jump):
| 	New functions.
| 	(image-mode): Set bookmark-make-cell-function appropriately.
| 
| 	* doc-view.el (doc-view-bookmark-jump): Correct misspelled arg name.
| 
| 	* bookmark.el (bookmark-make-cell-function): New variable.
| 	(bookmark-make): Call bookmark-make-cell-function's function
| 	instead of bookmark-make-cell.
| 	(bookmark-get-handler, bookmark-jump-internal): New functions.
| 	(bookmark-jump, bookmark-jump-other-window, bookmark-insert)
| 	(bookmark-bmenu-2-window, bookmark-bmenu-other-window):
| 	Use bookmark-jump-internal.
| 	(bookmark-make-cell-for-text-file): Rename from bookmark-make-cell.
| 
| 	* doc-view.el (doc-view-bookmark-make-cell)
| 	(doc-view-bookmark-jump): New functions.
| 	(doc-view-mode): Set bookmark-make-cell-function buffer-locally.
`----

And I don't see how it sets the name.  The name is set in `bookmark-set'
by querying the user and using a default value of the current bookmark
(if set) or the buffer name.

> Some people talk, some people work. :)

And others can't follow while others talk. :-)

Bye,
Tassilo
-- 
Richard Stallman has a katana. 'Nuff said.




  reply	other threads:[~2008-03-07 14:07 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 [this message]
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
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=87abla8w6b.fsf@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --cc=bzg@altern.org \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=reiner.steib@gmx.de \
    /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).