From: Stephen Berman <stephen.berman@gmx.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: New version of todo-mode.el (announcement + user guide)
Date: Thu, 13 Jun 2013 22:53:16 +0200 [thread overview]
Message-ID: <871u85d96r.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: jwvk3lyg6wg.fsf-monnier+emacs@gnu.org
On Wed, 12 Jun 2013 21:06:57 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> didn't consider the use-case you mention. I'll try to write a command
>> that converts from the new to the old format, but this may not be so
>
> Don't bother. A conversion forward is important, but a conversion
> backward much less so. Instead it's important to be able to use the
> old-style format in newer Emacsen.
>
>>> That sounds like the better solution. Even better if the old and the
>>> new code can be both in use at the same time (e.g. if you have
>>> converted some of your todo files but not all).
>> I want to be sure what you're saying here: are you saying there's
>> something better than making the old version obsolete? Or are you
>> saying it is ok to make it obsolete?
>
> Making it obsolete is fine.
>
>> (Your parenthetical example is a bit confusing, because the old
>> version only supports using one todo file at a time. I guess you
>> could have several todos files, but to switch between them you'd have
>> to unload todo-mode.el, change the value of todo-file-do and reload
>> the package. The fact that you can simultaneously use multiple todo
>> files is another big advantage of the new version -- and probably also
>> the main stumbling block in converting from the new to the
>> old format.)
>
> I was thinking of the case where the user wants to transition
> progressively, so she keeps her old-style todo file but also starts to
> use a new-style todo file.
> But maybe it's not important to support this use case.
>
>>> It sounds borderline.
>> That's a bit intimidating. Maybe the code Wolfgang Jenkner posted in
>> this thread could be used instead -- even better if it were just added
>> to Emacs. Juri Linkov also posted one a little while ago, which was
>> actually essentially the same as the Common Lisp recursive definition.
>> Is this really subject to copyright?
>
> No, it sounds fine, thank you. They're all sufficiently trivial.
Ok, thanks for the clarifications. As soon as the diary-lib issue is
resolved, I'll move on to installing the new version.
Steve Berman
next prev parent reply other threads:[~2013-06-13 20:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 23:31 New version of todo-mode.el (announcement + user guide) Stephen Berman
2013-06-10 13:24 ` Bastien
2013-06-10 14:35 ` Stephen Berman
2013-06-10 14:49 ` Bastien
2013-06-10 20:51 ` New version of todo-mode.el (code) Stephen Berman
2013-08-30 18:31 ` Jambunathan K
2013-09-08 21:09 ` Stephen Berman
2013-06-10 14:52 ` New version of todo-mode.el (announcement + user guide) Óscar Fuentes
2013-06-10 20:52 ` Stephen Berman
2013-06-11 0:20 ` Stefan Monnier
2013-06-11 18:36 ` Stephen Berman
2013-06-11 21:48 ` Stefan Monnier
2013-06-12 21:37 ` Stephen Berman
2013-06-13 1:06 ` Stefan Monnier
2013-06-13 20:53 ` Stephen Berman [this message]
2013-06-12 17:28 ` Glenn Morris
2013-06-12 21:26 ` Stefan Monnier
2013-06-12 21:37 ` Stephen Berman
2013-06-13 1:18 ` Stefan Monnier
2013-06-13 20:53 ` Stephen Berman
2013-06-14 0:21 ` Stefan Monnier
2013-06-14 21:37 ` Stephen Berman
2013-06-15 0:40 ` Glenn Morris
2013-06-15 1:49 ` Stefan Monnier
2013-06-15 12:52 ` Stephen Berman
2013-06-16 0:44 ` Stefan Monnier
2013-06-16 22:52 ` Stephen Berman
2013-06-17 0:37 ` Stefan Monnier
2013-06-17 19:50 ` Glenn Morris
2013-06-17 22:33 ` Stephen Berman
2013-06-12 18:30 ` Wolfgang Jenkner
2013-06-12 21:38 ` Stephen Berman
2013-06-13 1:24 ` Wolfgang Jenkner
2013-06-13 20:54 ` Stephen Berman
2013-06-13 10:59 ` Vitalie Spinu
2013-06-13 20:54 ` Stephen Berman
2013-08-31 3:55 ` 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=871u85d96r.fsf@rosalinde.fritz.box \
--to=stephen.berman@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).