From: Christian Moe <mail@christianmoe.com>
To: Tomer Altman <taltman@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Unable to use M-Ret from line-wrapped relative time items
Date: Sat, 16 Apr 2011 07:50:04 +0200 [thread overview]
Message-ID: <4DA92E0C.8030002@christianmoe.com> (raw)
In-Reply-To: <io4o98$c1m$1@dough.gmane.org>
Hi,
- I cannot reproduce the problem you describe (Org-mode 7.5, GNU Emacs
23.3.1 on Mac).
- Upgrading to Emacs 23 would probably be a good idea.
- Does the problem only happen when using timer items? The problem
appears to occur in org-list-struct. I'd expect it to happen to you
with description lists of any kind.
Yours,
Christian
On 4/13/11 7:59 PM, Tomer Altman wrote:
> Hi,
>
> I am an inexperienced org-mode user, so my apologies if this bug
> report falls short, or is submitted to the wrong forum.
>
> I've been experiencing an annoying bug/break since upgrading to
> OrgMode 7.5. I'm running it on GNU Emacs 22.3.1 (i386-apple-darwin9,
> Carbon Version 1.6.0).
>
> When I am using a relative timer, I can usually hit M-Ret at the end
> of the current item, to create a new time-stamped item (I'm using [X]
> for point):
>
> - 0:02:04 :: foo[X]
>
> This leads to a new timestamp item:
>
> - 0:02:04 :: foo
> - 0:02:06 ::
>
> But when the text of the second note gets to be too long, Emacs wraps
> the text to the next line (I have the Fill minor mode active). Trying
> to use M-Ret from the end of the second line of the second item leads
> to the attached break/backtrace:
>
> - 0:02:04 :: foo
> - 0:02:06 :: bar bar bar bar bar bar bar bar bar bar bar bar bar bar
> bar[X]
>
> Any ideas on how to fix this bug/break? Do I merely need to upgrade my
> version of GNU Emacs?
>
> Thank you for your time & help,
>
> ~Tomer
next prev parent reply other threads:[~2011-04-16 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 17:59 Unable to use M-Ret from line-wrapped relative time items Tomer Altman
2011-04-16 1:35 ` Tomer Altman
2011-04-16 2:23 ` Bernt Hansen
2011-04-16 5:50 ` Christian Moe [this message]
2011-04-16 7:28 ` Nicolas Goaziou
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DA92E0C.8030002@christianmoe.com \
--to=mail@christianmoe.com \
--cc=emacs-orgmode@gnu.org \
--cc=taltman@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/org-mode.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).