From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: Re: Long lines prevent Org mode!
Date: Wed, 08 Jan 2014 00:21:33 -0500 [thread overview]
Message-ID: <87ha9fvyjm.fsf@iro.umontreal.ca> (raw)
In-Reply-To: <87d2k313wc.fsf@gmail.com> (Nick Dokos's message of "Tue, 07 Jan 2014 23:41:39 -0500")
Nick Dokos <ndokos@gmail.com> writes:
> you can leave org out of the picture altogether: create an empty
> buffer, insert 33333 x's by hand, go to the beginning and evaluate
> (looking-at ".*foo")
> As Stefan says in the thread you pointed out, it's a limitation of the
> emacs regexp engine.
Yes, I got this from his article. However, it seems that "[^\nf]*foo"
would succeed, avoiding the stack explosion. So, it is possible to
rework the regexpes around the limitation.
Surely not a fun job to do for Org regexpes, I know. Maybe not worth
doing as very long lines are unusual, yet maybe worth doing nevertheless
for Org files because long lines are still possible. The fact is that I
was hit by this problem in the Org buffers generated by org-grep.
However, as I am tempted to think that the problem is unlikely to be
solved soon, I tried to alleviate it. org-grep now shortens the lines
by removing, within each line, a good part of the context between hits.
This does not guarantee that the above problem will never occur, but it
considerably decreases the chance that it occurs.
> I cut and paste and then use either C-c m (bound to
> message-mark-inserted-region) or C-c q (bound to boxquote-region)
Thanks for these hints, which I saved on keys here! :-)
> Of course, if your problem is that your mailer (or some mailer along
> the way) mangles the content, then the safest thing to do is to put it
> in an attachment or post it on some pastebin and send a link.
Sure.
My little problem was different. If I use Org in-line markup, like
bold, italics, or links to Web sites, or even block markup like
fragments between #+BEGIN_SRC and #+END_SRC, say, I was wondering how
this is best transmitted within a message, in the text, without
resorting to an attachment. Gnus as a reader surely has some capability
somewhere, as I think I saw messages displaying Org code nicely; I just
do not remember how it was done. Outside Gnus, it might be more
problematic to find a useful way to have Org included. Sending Org all
raw is sometimes a bit noisy, especially for links.
Someone recently mentioned org-mime.el, new to me, maybe this is the
proper avenue? I should at least play and experiment with it! :-).
François
next prev parent reply other threads:[~2014-01-08 5:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 1:24 Long lines prevent Org mode! François Pinard
2014-01-08 4:41 ` Nick Dokos
2014-01-08 5:21 ` François Pinard [this message]
2014-01-08 6:05 ` Nick Dokos
2014-01-08 9:18 ` Sebastien Vauban
2014-01-08 12:10 ` Nick Dokos
2014-01-08 12:29 ` François Pinard
2014-01-09 8:57 ` Sebastien Vauban
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=87ha9fvyjm.fsf@iro.umontreal.ca \
--to=pinard@iro.umontreal.ca \
--cc=emacs-orgmode@gnu.org \
/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).