Applied, thanks.
- Carsten
On May 7, 2010, at 6:03 PM, David Maus wrote:
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report?
See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report wi
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
-
Hi David,
I have applied your patch, thanks!
- Carsten
On Dec 5, 2009, at 10:03 PM, David Maus wrote:
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report?
See
http://orgmode.org/manual/Feedback.htm
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
-
On Nov 26, 2009, at 11:04 PM, David Maus wrote:
Hi Carsten,
At Thu, 26 Nov 2009 08:42:09 +0100,
Carsten Dominik wrote:
Hi David,
you cannot reasonably expect that org-mode functions should work
in other modes. And you cannot expect these functions to check
the mode all the time.
I don't kn
Hi Carsten,
At Thu, 26 Nov 2009 08:42:09 +0100,
Carsten Dominik wrote:
> Hi David,
>
> you cannot reasonably expect that org-mode functions should work
> in other modes. And you cannot expect these functions to check
> the mode all the time.
>
> I don't know what you are up to here. But maybe
On Nov 25, 2009, at 9:05 AM, David Maus wrote:
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report?
See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mod
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
-
Carsten Dominik writes:
> I have reverted this commit, thanks.
Thanks! It works again for me :)
-Bernt
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo
I have reverted this commit, thanks.
In particular thanks for finding the commit. Just saying "stuck
projects"
would have sent me off in the wrong direction.
- Carsten
On Apr 3, 2009, at 3:53 PM, Bernt Hansen wrote:
Hi Carsten,
The following commit breaks finding stuck projects for me.
Hi Carsten,
The following commit breaks finding stuck projects for me. It looks
like an infinite loop.
commit 1fbe1f7f503e473e6a3a14f44451c4e6e5f043a4
Author: Carsten Dominik
Date: Thu Apr 2 18:16:35 2009 +0200
Tags
Fixed, thanks.
- Carsten
On Apr 11, 2007, at 22:06, Leo wrote:
Another bug in 4.70.
before the first level-1 heading, typing "M-RET" will enter emacs into
infinite loop.
,[ Backtrace ]
| Debugger entered--Lisp error: (quit)
| looking-at("[ ]*$")
| (if (looking-at "[ ]*$") (setq ind
On Wed, 2007-04-11 at 21:06 +0100, Leo wrote:
> before the first level-1 heading, typing "M-RET" will enter emacs into
> infinite loop.
I can confirm this.
--
+---+
| Jason F. McBrayer[EMAIL PROTECTED] |
| If someone c
Another bug in 4.70.
before the first level-1 heading, typing "M-RET" will enter emacs into
infinite loop.
,[ Backtrace ]
| Debugger entered--Lisp error: (quit)
| looking-at("[ ]*$")
| (if (looking-at "[ ]*$") (setq ind1 ind-empty) (skip-chars-forward "
") (setq ind1 (curren
14 matches
Mail list logo
