From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Fran=C3=A7ois_Pinard?= Subject: Re: Long lines prevent Org mode! Date: Wed, 08 Jan 2014 00:21:33 -0500 Message-ID: <87ha9fvyjm.fsf@iro.umontreal.ca> References: <87txdfw9ij.fsf@iro.umontreal.ca> <87d2k313wc.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33032) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0laH-0002SJ-GV for emacs-orgmode@gnu.org; Wed, 08 Jan 2014 00:21:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W0laA-0005ng-Si for emacs-orgmode@gnu.org; Wed, 08 Jan 2014 00:21:41 -0500 Received: from 206-248-137-202.dsl.teksavvy.com ([206.248.137.202]:61391 helo=mercure.progiciels-bpi.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W0laA-0005mi-MX for emacs-orgmode@gnu.org; Wed, 08 Jan 2014 00:21:34 -0500 In-Reply-To: <87d2k313wc.fsf@gmail.com> (Nick Dokos's message of "Tue, 07 Jan 2014 23:41:39 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Nick Dokos 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=C3=A7ois