From: Michael Brand <firstname.lastname@example.org>
To: Peter Salazar <email@example.com>
Cc: Org Mode <firstname.lastname@example.org>
Subject: Re: hidestarsfile: "hidestars" for file
Date: Sun, 26 Feb 2012 16:50:52 +0100 [thread overview]
Message-ID: <CALn3zoiQGPzHca0Se1LZDnSpbSbq3YX0ZL_P-GeNRrDG3Zg6BQ@mail.gmail.com> (raw)
Thanks for testing hidestarsfile. I just published fileconversion
version 0.2 (generalized name and functionality) with a speed-up 
and many other improvements. So please check out again:
> [...] Even better would be if the
> stars showed up as # so they'd be readable with Markdown.
Nice idea and implemented with the new generalisation of
my-org-fileconversion-* that is now extensible.
Take care that you don't end up hooking a complete file format
conversion to and from a format by calling pandoc and Org export or
> It turns out the spinning pinwheel was due to an incompatibility
> between the new version of org-mode and a function I'm running called
> hidestarsfile, which made my .org files nice and readable in other
> text editors.
> Hidestarsfile worked fine with my old org-mode, but for some reason
> with the new version it causes endless pinwheeling. I removed that
> function from my .emacs file and now everything is running smoothly.
I could not reproduce this with Aquamacs 2.1 and org-version 7.8.03
(release_7.8.03-258-g263cb.dirty). What is the backtrace when you set
debug-on-quit to t and stop the pinwheel with "C-g C-g"?
 hidestarsfile now uses less CPU time than the rest of Org mode for
all of some typical Org files that I profiled during find-file.
prev parent reply other threads:[~2012-02-26 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 16:43 hidestarsfile: "hidestars" for file Michael Brand
2012-02-09 18:57 ` Michael Brand
2012-02-16 17:53 ` Michael Brand
2012-02-26 15:50 ` Michael Brand [this message]
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).