all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Fri, 23 May 2014 18:59:46 +0200	[thread overview]
Message-ID: <87ppj4e8hp.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <87bnv0xhf3.fsf@rosalinde.fritz.box> (Stephen Berman's message of "Wed, 14 May 2014 21:57:04 +0200")

On Wed, 14 May 2014 21:57:04 +0200 Stephen Berman <stephen.berman@gmx.net> wrote:

> 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

On Wed, 14 May 2014 22:24:41 -0400 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:

>> Ok, I understand (that also answers a question I was tempted to ask you
>> about why SES files don't violate your design goals).  But I would
>> consider this to be a new feature (which I still have doubts about),
>> which could be considered for the trunk, but not for emacs-24.  In
>> contrast, the use of auto-mode-alist is a bug-inducing misfeature and
>> should be removed before the release.
>
> Sounds OK.

The required changes to remove the use of auto-mode-alist amount mainly
to calling the appropriate Todo mode function when visting a Todo file,
if it isn't already in that mode, so in view of Stefan's approval of the
plan not to use auto-mode-alist here, I've refrained from posting the
patch and simply committed it.

Glenn, if you want to test and (hopefully) confirm that this bug is
fixed, I'll wait for your response; otherwise, I'll take the liberty of
closing it in a day or two.

Besides fixing this bug, in the process of making and testing the
changes I found a handful of other bugs, which I've already fixed in a
separate changeset (bzr 117142 in emacs-24).

Steve Berman





  parent reply	other threads:[~2014-05-23 16:59 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ppj4e8hp.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.