From: Karl Fogel <kfogel@red-bean.com>
To: Pierre-Yves Luyten <py@luyten.fr>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] open bookmark in other frame
Date: Fri, 02 Nov 2018 13:55:40 -0500 [thread overview]
Message-ID: <87k1lv5mxf.fsf@red-bean.com> (raw)
In-Reply-To: <6a73c984-002a-f767-6a96-3fb0822489de@luyten.fr> (Pierre-Yves Luyten's message of "Sun, 14 Oct 2018 21:45:55 +0200")
Pierre-Yves Luyten <py@luyten.fr> writes:
>Hello, here is the change in one single patch, and a few changes to
>commit message.
Hi, Pierre-Yves.
It's always a good idea to test changes in a freshly-built and freshly-started Emacs. In this case, because there was no ";;;###autoload" marker before `bookmark-jump-other-frame', invoking that function in a fresh Emacs would generate an error. For example, for me `bookmark-map' is bound to `C-c B', so when I did `C-c B 5' (in a new Emacs) I got an error.
The fix is simple -- this change on top of your patch:
--- lisp/bookmark.el
+++ lisp/bookmark.el
@@ -1125,6 +1125,7 @@ bookmark-jump-other-window
bookmark-current-bookmark)))
(bookmark-jump bookmark 'switch-to-buffer-other-window))
+;;;###autoload
(defun bookmark-jump-other-frame (bookmark)
"Jump to BOOKMARK in another frame. See `bookmark-jump' for more."
(interactive
Obviously, I could just add that ";;;###autoload" line myself commit your patch. But I thought you might want a chance to update the patch and re-post it, so that you'd have the experience of trying the change before and after. Either way is fine with me; let me know what you'd like to do.
(If you're not familiar with what the autoload system does, see section 16.5 "Autoload" in the Info pages.)
Best regards,
-Karl
next prev parent reply other threads:[~2018-11-02 18:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 20:14 [PATCH] open bookmark in other frame Pierre-Yves Luyten
2018-10-10 20:16 ` Marcin Borkowski
2018-10-10 21:35 ` Karl Fogel
2018-10-11 11:42 ` Pierre-Yves Luyten
2018-10-10 22:06 ` Drew Adams
2018-10-11 7:19 ` Karl Fogel
2018-10-11 11:30 ` Pierre-Yves Luyten
2018-10-11 13:35 ` Drew Adams
2018-10-11 21:50 ` Pierre-Yves Luyten
2018-10-11 22:04 ` Drew Adams
2018-10-12 19:45 ` Pierre-Yves Luyten
2018-10-12 21:23 ` Karl Fogel
2018-10-14 19:45 ` Pierre-Yves Luyten
2018-10-16 2:09 ` Karl Fogel
2018-10-16 9:51 ` Pierre-Yves Luyten
2018-10-16 2:10 ` Karl Fogel
2018-11-02 18:55 ` Karl Fogel [this message]
2018-11-04 21:10 ` Pierre-Yves Luyten
2018-11-09 0:54 ` Karl Fogel
2018-10-13 15:04 ` Stephen Leake
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=87k1lv5mxf.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-devel@gnu.org \
--cc=py@luyten.fr \
/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).