From: Wes Hardaker <wjhns209@hardakers.net>
To: James TD Smith <ahktenzero@mohorovi.cc>
Cc: emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: Re: Suggestion with bad patch for org-remember-templates
Date: Mon, 05 Jan 2009 08:30:32 -0800 [thread overview]
Message-ID: <sdvdstlnpz.fsf@wes.hardakers.net> (raw)
In-Reply-To: <20090103184536.GA2267@yog-sothoth.mohorovi.cc> (James TD Smith's message of "Sat, 3 Jan 2009 18:45:36 +0000")
>>>>> On Sat, 3 Jan 2009 18:45:36 +0000, James TD Smith <ahktenzero@mohorovi.cc> said:
JTS> I think I'm about 2/3rds of the way through the refactoring and
JTS> adding plist templates.
Thanks for the updates to both of you and I'm very much looking forward
to the new code!
One of the reasons that I have so many remember templates is I almost
always have 2 per subject: one that includes a link to the current spot
in the current buffer and one that doesn't. Having a multi-stage
selection would certainly fix that aspect of the problem.
JTS> I have auto-expanding minibuffers turned on (Emacs 22.2) and
JTS> haven't noticed any problems with them, so I'd suggest Wes give
JTS> them another try.
FYI, this was under XEmacs and it was a number of years ago (10+
probably) where if you had too long of a potential buffer it would crash
XEmacs (probably when the mini buffer needed to be larger than the
original window size or something).
I'll try again...
--
"In the bathtub of history the truth is harder to hold than the soap,
and much more difficult to find." -- Terry Pratchett
prev parent reply other threads:[~2009-01-05 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 15:39 Suggestion with bad patch for org-remember-templates Wes Hardaker
2009-01-03 17:26 ` Carsten Dominik
2009-01-03 18:45 ` James TD Smith
2009-01-04 7:23 ` Carsten Dominik
2009-01-05 16:31 ` Wes Hardaker
2009-01-05 18:41 ` Carsten Dominik
2009-01-06 14:32 ` Wes Hardaker
2009-01-06 15:17 ` Carsten Dominik
2009-01-06 23:06 ` James TD Smith
2009-01-05 16:30 ` Wes Hardaker [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=sdvdstlnpz.fsf@wes.hardakers.net \
--to=wjhns209@hardakers.net \
--cc=ahktenzero@mohorovi.cc \
--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).