From: Stephen Berman <stephen.berman@gmx.net>
To: Glenn Morris <rgm@gnu.org>
Cc: 17482@debbugs.gnu.org
Subject: bug#17482: args-out-of-range when visiting foo.todo
Date: Wed, 14 May 2014 21:57:04 +0200 [thread overview]
Message-ID: <87bnv0xhf3.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <p5egzwp81y.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 14 May 2014 13:46:33 -0400")
On Wed, 14 May 2014 13:46:33 -0400 Glenn Morris <rgm@gnu.org> wrote:
> Stefan Monnier wrote:
>
>> Maybe a quick way to "reach" the design goal is to wrap the body of
>> todo-mode in a `with-demoted-errors'.
>
> It's better, but I think it's still not great if I visit blah.todo and
> get "args-out-of-range" as a message rather than an error.
I agree. Moreover, if blah.todo is not empty but not a valid Todo file,
visiting it will raise a different error from a different part of the
code, so it would be necessary to have multiple uses of
`with-demoted-errors'. And there's still the issue of why *.todo files
not in `todo-directory' should be in Todo mode. And the only sensible
answer is: they shouldn't be. So I am convinced that todo-mode should
not use auto-mode-alist: it's not needed and it only causes problems. I
somehow became blinded by the idea that it's nice to be able to visit a
todo-mode file with `find-file' or from Dired and have it be in
todo-mode and display properly, but this was just a mistake and now I've
seen the light. So unless there's a really good reason not to, I'll go
ahead and excise the use of auto-mode-alist; I'll post a patch for
review before committing.
Steve Berman
next prev parent reply other threads:[~2014-05-14 19:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 6:22 bug#17482: args-out-of-range when visiting foo.todo Glenn Morris
2014-05-13 15:57 ` Stephen Berman
2014-05-13 16:02 ` Glenn Morris
2014-05-13 16:26 ` Stephen Berman
2014-05-13 19:40 ` Stefan Monnier
2014-05-13 22:33 ` Stephen Berman
2014-05-14 3:22 ` Stefan Monnier
2014-05-14 15:10 ` Stephen Berman
2014-05-14 16:55 ` Stefan Monnier
2014-05-14 17:46 ` Glenn Morris
2014-05-14 19:57 ` Stephen Berman [this message]
2014-05-14 20:01 ` Glenn Morris
2014-05-14 20:34 ` Stephen Berman
2014-05-14 21:44 ` Stefan Monnier
2014-05-14 21:58 ` Stephen Berman
2014-05-15 2:24 ` Stefan Monnier
2014-05-23 16:59 ` Stephen Berman
2014-05-23 17:32 ` Glenn Morris
2014-05-23 19:12 ` Stephen Berman
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=87bnv0xhf3.fsf@rosalinde.fritz.box \
--to=stephen.berman@gmx.net \
--cc=17482@debbugs.gnu.org \
--cc=rgm@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.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).