unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Michal Nazarewicz <mina86@mina86.com>
Cc: Ted Zlatanov <tzz@lifelogs.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: [PATCH] Add `notes' function to store random notes across Emacs restarts.
Date: Mon, 17 Jun 2013 23:06:02 +0200	[thread overview]
Message-ID: <CAAeL0SQOJgYwgEERmP8v7ftZtjEx2h8wy3hrL9UnoOJgZmrKxg@mail.gmail.com> (raw)
In-Reply-To: <xa1tobb4o4j7.fsf@mina86.com>

On Mon, Jun 17, 2013 at 10:39 PM, Michal Nazarewicz <mina86@mina86.com> wrote:

>> Use \\[notes-save-and-bury] instead of hard-coded C-c C-c
>
> I'm not certain how that's supposed to work.  The binding is not in
> global key map after all.

Adding \\<notes-map> to the docstring should work. (elisp) "24.3
Substituting Key Bindings in Documentation":

`\<MAPVAR>'
     stands for no text itself.  It is used only for a side effect: it
     specifies MAPVAR's value as the keymap for any following
     `\[COMMAND]' sequences in this documentation string.


> Because kill-buffer-hook is called after kill-buffer checks whether file
> is modified:

Hmm. You're right. Weird to have to resort to an advice.

   J



  reply	other threads:[~2013-06-17 21:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17 16:13 [PATCH] Add `notes' function to store random notes across Emacs restarts Michal Nazarewicz
2013-06-17 16:44 ` Stefan Monnier
2013-06-17 20:24   ` Michal Nazarewicz
2013-06-17 17:00 ` Juanma Barranquero
2013-06-17 20:39   ` Michal Nazarewicz
2013-06-17 21:06     ` Juanma Barranquero [this message]
2013-06-17 23:47       ` Michal Nazarewicz
2013-06-18  7:20         ` martin rudalics
2013-06-18 12:24           ` Michal Nazarewicz

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=CAAeL0SQOJgYwgEERmP8v7ftZtjEx2h8wy3hrL9UnoOJgZmrKxg@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=mina86@mina86.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=tzz@lifelogs.com \
    /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).