Matthew MacLean writes:
> No worries. If anything it makes be feel better about my own
> silliness earlier.
Well, I'm good at making people feeling better about their own
silliness, so you're most welcome.
--
Bastien
No worries. If anything it makes be feel better about my own silliness
earlier.
On Tue, Aug 18, 2015 at 11:54 AM, Bastien wrote:
> Matthew MacLean writes:
>
> > Maybe the recursive-whitespace Regular Expressions that Pip Cet
> > mentioned are not Emacs freezers in Emacs 25?
>
> No... this is ju
I'm using Emacs 25.0.50.26, for what it's worth, and they still freeze
Emacs here. I don't recall precisely when the problematic regular
expressions were introduced, though, that might have been after 8.3.1?
On 8/18/15, Matthew MacLean wrote:
> Fascinating.
>
> Maybe the recursive-whitespace Regu
Matthew MacLean writes:
> Maybe the recursive-whitespace Regular Expressions that Pip Cet
> mentioned are not Emacs freezers in Emacs 25?
No... this is just me using the patched version, sorry for the noise.
--
Bastien
Fascinating.
Maybe the recursive-whitespace Regular Expressions that Pip Cet mentioned
are not Emacs freezers in Emacs 25?
On Tue, Aug 18, 2015 at 11:30 AM, Bastien wrote:
> Hi Matthew,
>
> I've no problem with the link in hang.org.
>
> This is with Org 8.3.1 and Emacs 25.0.50.18.
>
> --
> Bas
Hi Matthew,
I've no problem with the link in hang.org.
This is with Org 8.3.1 and Emacs 25.0.50.18.
--
Bastien
Pip Cet writes:
> Of course, here we go. Please let me know if there's anything wrong
> with it still. (I don't think gmail copy-and-paste preserves tabs, so
> this is sent as an attachment. Is that okay, for future reference?)
>
> It would be great if README_contribute could be updated no longer
Hi Nicolas,
On Thu, Aug 13, 2015 at 11:37 PM, Nicolas Goaziou
wrote:
> Hello,
>
> Pip Cet writes:
>
>> Can you try this patch? That appears to fix the issue here, at least
>> for this one file, at the cost of yet another shy group added to the
>> regular expression.
>
> Thanks for the patch.
>
>
Hello,
Pip Cet writes:
> Can you try this patch? That appears to fix the issue here, at least
> for this one file, at the cost of yet another shy group added to the
> regular expression.
Thanks for the patch.
Would you mind providing a proper commit message and send it again using
"git format-
Yep! This patch works on the original file I noticed the behaviour.
On Thu, Aug 13, 2015 at 12:50 PM, Pip Cet wrote:
> (Sorry if this arrives in duplicate, I had neglected to configure
> Gmail to default to reply-to-all behaviour).
>
I did that earlier as well, it's a curse!
Can you try this patch? That appears to fix the issue here, at least
for this one file, at the cost of yet another shy group added to the
regular expression.
diff --git a/lisp/org.el b/lisp/org.el
index a908d9e..7f46687 100755
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -11128,18 +11128,18 @@ of matche
On Thu, Aug 13, 2015 at 12:26 PM, Pip Cet wrote:
> It's not an Emacs bug. Your regular expression whittles down to:
>
> (defvar hang-re "^\\*+ *Mawile\\(?:[ ]+\\)+stuff\\(?:[ ]+\\)*$")
>
> or even
>
> (defvar hang-re "\\(?:[ ]+\\)+s")
>
> That expression matches the string of spaces separating th
So, I found a hang in org-link-search... (In what I think is an Emacs bug,
but posting this here certainly can't hurt.)
When you have a headline with a tag (For example "Mawile" with
":something:" as a tag), and another headline later in the buffer beginning
with the other headline's title within
13 matches
Mail list logo
