From: Stephen Berman <stephen.berman@gmx.net>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 15225@debbugs.gnu.org
Subject: bug#15225: 24.3.50; todo-mode: Some bugs and suggestions
Date: Sun, 08 Sep 2013 23:08:04 +0200 [thread overview]
Message-ID: <87ob833tu3.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <BLU0-SMTP434CD292F2D127A65E9A0C691350@phx.gbl>
On Sat, 31 Aug 2013 18:09:28 +0530 Jambunathan K <kjambunathan@gmail.com> wrote:
> 1. `e m' on an item
> 2. C-x b
> 3. `e e' on an item
>
> See the following:
>
> todo-edit-multiline-item: Buffer name `*Todo Edit*' is in use [4
> times]
This only happens with the above recipe if the item in step 1 is a
multiline item and in step 3 you type `e e' on the same item. It also
happens if in step 3 you type `e m' instead of `e e', and then it
doesn't matter whether the item is the same. The reason is because
todo-edit-multiline-item (bound to `e m') uses an indirect buffer (and
todo-edit-item (bound to `e e') calls todo-edit-multiline-item if the
item is multiline), and currently allows only a single instance, named
*Todo Edit*.
> I would expect that it switch to the buffer instead.
This is a reasonable expectation, but I think it's a bit involved to
implement correctly, because you have to keep track of which item from
the Todo mode buffer is associated with which indirect buffer, whose
content may have changed. I think I can make it work, but is it really
important to you to be able to have multiple item editing buffers? In
terms of key strokes, there's little difference between `C-x b'+`e m'
and `C-x C-q'+`e m'. (I understand from your other post that you'd
prefer to edit multiple items in a single buffer, but that's a different
functionality.)
> ----------------------------------------------------------------
>
> This is an error that occurs frequently and has made my todo file
> practically unusable.
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> expand-file-name(nil)
> find-file-noselect(nil nowarn)
> todo-mode-external-set()
> todo-edit-mode()
> todo-edit-multiline-item()
> call-interactively(todo-edit-multiline-item nil nil)
> command-execute(todo-edit-multiline-item)
>
> Once such a thing happens the todo file which was good to begin with
> gets screwed and I really can do nothing more with it.
The only thing I can say for sure here is that this happens because
find-file-noselect tries to find the current todo file but for some
reason there is none. This is certainly a bug, but to debug it I really
need a reproducible recipe.
> My STRONG RECOMMENDATION
>
> To the users:
>
> - Beware of todo-mode to create real life todo entries. It will make
> you pay for it.
I'll do my best to lower the cost where I can. Can you tell me
specifically what you consider overpriced?
> To the maintainer:
>
> - PLEASE! Compute the sexp for categories on demand. Do you really
> think that pre-computation is very much necessary speed up things on
> large todo lists.
I'm not sure it is, but I tried to use the stored value only where
on-the-fly computation wasn't necessary. Is there some place you think
I missed?
Steve Berman
next prev parent reply other threads:[~2013-09-08 21:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 18:18 bug#15225: 24.3.50; todo-mode: Some bugs and suggestions Kanthimathi R
2013-08-31 4:07 ` Jambunathan K
2013-08-31 12:39 ` Jambunathan K
2013-09-08 21:08 ` Stephen Berman [this message]
2013-09-08 21:08 ` Stephen Berman
2013-09-08 21:07 ` Stephen Berman
2013-12-20 17:44 ` Stephen Berman
2013-12-21 2:50 ` Jambunathan K
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=87ob833tu3.fsf@rosalinde.fritz.box \
--to=stephen.berman@gmx.net \
--cc=15225@debbugs.gnu.org \
--cc=kjambunathan@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 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).