From: Nicolas <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>
Subject: Re: Timer mode doesn't hyphenate correctly
Date: Thu, 31 Mar 2011 14:00:26 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Mark S.'s message of "Wed, 30 Mar 2011 21:39:39 -0800")
"Mark S" <firstname.lastname@example.org> writes:
> Hello Matt,
> --- On Wed, 3/30/11, Matt Lundin <email@example.com> wrote:
>>I cannot reproduce this.
>>All of the following timer items were entered quickly using
>> - 0:01:04 :: An item
>> - 0:01:07 :: Another item
>> - 0:01:10 :: Yet another
> It appears that you can get different results depending on how you
> start the timer and whether there are prior entries there. Basically,
> you need to start on a blank line with no prior timing entries. If you
> start your timer, either with C-c C-x 0 or with C-c C-x - with prior
> timer entries, you are likely to get the results I described before
> (double hyphens), or error messages ("not a timer list").
> So to people who know the right incantation, I suppose it looks ok.
> But if you take even a slight detour you may get some strange results.
> Maybe there should be a bit more warning in the manual. But now that
> I've worked out the land-mines, I'm sure its going to be very useful.
I cannot reproduce what you are describing. I may be misunderstanding
you. Could you please post an ECM for that?
next prev parent reply other threads:[~2011-03-31 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 5:39 Re: Timer mode doesn't hyphenate correctly Mark S
2011-03-31 12:00 ` Nicolas [this message]
2011-04-01 4:46 ` Mark S
2011-04-01 6:32 ` Nicolas
2011-04-01 13:02 ` Mark S
2011-04-01 15:21 ` Nicolas
-- strict thread matches above, loose matches on Subject: below --
2011-03-30 20:40 Mark S
2011-03-31 1:01 ` Matt Lundin
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).