From: Jambunathan K <kjambunathan@gmail.com>
To: Bastien <bzg@altern.org>
Cc: "\\\"François\\\" Pinard" <pinard@iro.umontreal.ca>,
nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Killed Org files referred from the agenda?
Date: Fri, 13 Apr 2012 15:51:05 +0530 [thread overview]
Message-ID: <81iph4x78u.fsf@gmail.com> (raw)
In-Reply-To: <878vi0jjjz.fsf@altern.org> (Bastien's message of "Fri, 13 Apr 2012 07:07:22 +0200")
,----[ C-h f emacs-lock-mode RET ]
| emacs-lock-mode is an interactive autoloaded Lisp function in
| `emacs-lock.el'.
|
| (emacs-lock-mode &optional ARG)
|
| Toggle Emacs Lock mode in the current buffer.
| If called with a plain prefix argument, ask for the locking mode
| to be used. With any other prefix ARG, turn mode on if ARG is
| positive, off otherwise. If called from Lisp, enable the mode if
| ARG is omitted or nil.
|
| Initially, if the user does not pass an explicit locking mode, it
| defaults to `emacs-lock-default-locking-mode' (which see);
| afterwards, the locking mode most recently set on the buffer is
| used instead.
|
| When called from Elisp code, ARG can be any locking mode:
|
| exit -- Emacs cannot exit while the buffer is locked
| kill -- the buffer cannot be killed, but Emacs can exit as usual
| all -- the buffer is locked against both actions
|
| Other values are interpreted as usual.
|
| [back]
`----
Emacs-24.1 has the following NEWS entry.
,----
| ** New emacs-lock.el package.
| (The previous version has been moved to obsolete/old-emacs-lock.el.)
| Now, there is a proper minor mode `emacs-lock-mode'.
| Protection against exiting Emacs and killing the buffer can be set
| separately. The mechanism for automatically turning off protection
| for buffers with dead inferior processes has been generalized.
`----
--
prev parent reply other threads:[~2012-04-13 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 15:20 Killed Org files referred from the agenda? François Pinard
2012-04-12 16:02 ` Nick Dokos
2012-04-12 16:37 ` François Pinard
2012-04-12 16:56 ` Bernt Hansen
2012-04-12 19:30 ` Nick Dokos
2012-04-13 5:07 ` Bastien
2012-04-13 10:21 ` Jambunathan K [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81iph4x78u.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
--cc=pinard@iro.umontreal.ca \
/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/org-mode.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).