From: Nicolas Goaziou <firstname.lastname@example.org>
To: Carsten Dominik <email@example.com>
Cc: Bernt Hansen <firstname.lastname@example.org>, Org Mode List <email@example.com>
Subject: Re: [dev] org-indent-mode patch
Date: Thu, 18 Aug 2011 12:19:07 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <031BF3EE-4DCC-4AE9-BA36-43380408806C@gmail.com> (Carsten Dominik's message of "Thu, 18 Aug 2011 10:38:29 +0200")
Carsten Dominik <email@example.com> writes:
> what has happened to this patch? Did you stop it due to my questions?
> That was not my intention - so if you are convinced that it works well,
> it might be a good solution.
> On Jul 21, 2011, at 5:14 PM, Nicolas Goaziou wrote:
>> In order to circumvent the slow process at initialization, I've
>> implemented an asynchronous initialization. Thus, one can open the
>> buffer and start to write in it before initialization is complete. Once
>> it is done, everything else is synchronous again.
>> I think it is a good compromise. It needs testing though. Thus, if
>> anyone is interested, I'll gladly hear his feedback.
>> The branch is located at :
>> git://github.com/ngz/org-mode-lists.git indent-patch-no-timer
It's still there. As I use neither Org indent mode nor Visual line mode,
feedback is important. Have you tried it since asynchronous
initialization implementation? Does it solve the problems you raised?
Bernt Hansen has been testing it for a few weeks now. As far as I know,
he hasn't encountered any problem so far.
next prev parent reply other threads:[~2011-08-18 10:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-13 16:21 [dev] org-indent-mode patch Nicolas
2011-03-14 7:51 ` Carsten Dominik
2011-03-19 6:33 ` Linus Arver
2011-07-21 15:14 ` Nicolas Goaziou
2011-08-18 8:38 ` Carsten Dominik
2011-08-18 10:19 ` Nicolas Goaziou [this message]
2011-08-18 10:26 ` Carsten Dominik
2011-08-18 12:02 ` Bernt Hansen
2011-08-18 12:55 ` Bastien
2011-08-18 14:00 ` Nicolas Goaziou
2011-08-18 16:47 ` Bastien
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).