From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: emacs-lock enhancements
Date: Tue, 22 Sep 2009 11:02:13 -0400 [thread overview]
Message-ID: <jwvskefowqg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <f7ccd24b0909220354p1f390b00t4b1272f011f44632@mail.gmail.com> (Juanma Barranquero's message of "Tue, 22 Sep 2009 12:54:03 +0200")
> I'm interested in incorporating into Emacs some of the functionality
> (not code) of Noah Friedman's protbuf.el, i.e., the ability to protect
> a buffer against killing.
We already have a fair bit of Noah's code, so at least from a copyright
point of view, copying code shouldn't be a problem (we'd still need Noah
to agreed, of course, but the prognosis is pretty good).
Of course, reimplementing might actually be simpler from a technical
point of view.
> Currently, emacs-lock.el does something similar, though it has some problems:
> - It's not a proper minor-mode, so the locked status doesn't show in
> the modeline.
It would be good to fix it so it uses define-minor-mode.
> - It deals with telnet and shell buffers as special cases, instead of
> handling all buffers with live processes.
Sounds like it would be good to improve that as well.
> What is the best interface for that: having two different minor modes
> (let's say "emacs-lock-dont-kill-mode' and
> `emacs-lock-dont-exit-mode'), or just one and somehow setting a flag
> to indicate the desired level of protection, sort of like
> overwrite-mode distinguishes between "normal" and "binary" modes?
I single major mode sounds sufficient. The distinction between the two
cases could even be done with a global variable, rather than being
per-buffer.
Stefan
next prev parent reply other threads:[~2009-09-22 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 10:54 emacs-lock enhancements Juanma Barranquero
2009-09-22 15:02 ` Stefan Monnier [this message]
2009-09-22 15:08 ` Juanma Barranquero
2009-09-22 16:27 ` 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=jwvskefowqg.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.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 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.