From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: a small remember suggestion
Date: Sat, 21 Mar 2009 12:28:46 -0700 [thread overview]
Message-ID: <20524da70903211228o8ef4b21pc9a287ecd923383c@mail.gmail.com> (raw)
org-remember -- use a file
On more than one occasion, I have composed something using
org-remember, and mistakenly hit a key for killing the
buffer. With all buffers except org-remember, this kills a
buffer if it has no unsaved text, and asks what buffer to
kill if it does, at which point I quit.
With org-remember, the buffer has unsaved text, but it is
not associated with a file, so it loses text.
Text is probably lost upon a crash also.
My suggestion is this. Perhaps org-remember can have a file
(this fixes the killing problem), and that file can be
autosaved (this fixes the crash problem).[fn:4]
There is one more case in which text is lost. You might run
org-remember from org-remember and not undo. My existing
proposal is to allow calling o-r from o-r. I think that
solves it. In such a case, however, it will be necessary
to allow more than one such file.
[fn:4] In principle, if the target location is known, the
file can be an indirect buffer into that buffer. This has
other advantages, including having all in-buffer settings
work, being able to isearch, having a crashed org-remember
stay where it is supposed to be (albeit unfinished) and so
on. But it wouldn't be necessary to get that fancy. Just
any file would work.
--
Myalgic encephalomyelitis denialism is causing death (decades early;
Jason et al. 2006) and severe suffering (worse than nearly all other
diseases studied; e.g. Schweitzer et al. 1995) and grossly corrupting
science. http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm
next reply other threads:[~2009-03-21 19:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 19:28 Samuel Wales [this message]
[not found] ` <7bef1f890903211425p1b1329ebxd42b3d7c1a3a77d7@mail.gmail.com>
2009-03-22 2:01 ` a small remember suggestion Alan E. Davis
2009-03-22 15:16 ` Carsten Dominik
2009-03-22 17:03 ` Richard Riley
2009-03-22 20:36 ` Alan E. Davis
2009-03-24 3:29 ` Samuel Wales
2009-03-24 3:42 ` Samuel Wales
2009-03-24 11:29 ` Carsten Dominik
2009-03-24 11:29 ` Carsten Dominik
2009-03-24 14:22 ` Alan E. Davis
2009-03-25 8:22 ` Carsten Dominik
2009-03-25 4:46 ` Samuel Wales
2009-03-25 6:24 ` Alan E. Davis
2009-03-25 8:23 ` Carsten Dominik
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=20524da70903211228o8ef4b21pc9a287ecd923383c@mail.gmail.com \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).