Re: [Orgmode] Cycling visibility of blocks

2009-06-02 Thread Carsten Dominik
Applied, thanks. - Carsten On Jun 2, 2009, at 6:47 PM, Eric Schulte wrote: Good catch, I'm not sure what is causing this problem, but the attached patch which changes the regexp seems to solve it. Thanks -- Eric diff --git a/lisp/org.el b/lisp/org.el index 1c3dfe5..6792bed 100644 --- a/

Re: [Orgmode] Cycling visibility of blocks

2009-06-02 Thread Nicolas Goaziou
Hum, 1. My apologies for the From: header in my previous post, I just realized I had messed up badly with my gnus-posting-style variable; 2. While I'm at it: two line --> two lines. -- Nicolas Goaziou ___ Emacs-orgmode mailing list Remember: use

Re: [Orgmode] Cycling visibility of blocks

2009-06-02 Thread Eric Schulte
Good catch, I'm not sure what is causing this problem, but the attached patch which changes the regexp seems to solve it. Thanks -- Eric diff --git a/lisp/org.el b/lisp/org.el index 1c3dfe5..6792bed 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -5146,8 +5146,7 @@ Optional argument N means, put

Re: [Orgmode] Cycling visibility of blocks

2009-06-02 Thread Carsten Dominik
Hello, Isn't there something wrong with the regexp as the snippet is not working well when #+END_SOMETHING is followed right away by a new line ? I mean #+BEGIN_QUOTE Test etn ntes thens hsne htsne nste thnes sne thsne htse nthes ehtse hntse hents #+END_QUOTE  <--- notice the space Bla

Re: [Orgmode] Cycling visibility of blocks

2009-05-26 Thread Eric Schulte
Sebastian Rose writes: > "Eric Schulte" writes: >> I've applied a slightly changed version of your regexp, and this is now >> working for all block types (the resulting file is attached). Where >> could this file be saved? The contrib directory seems like overkill for >> such a small piece of

Re: [Orgmode] Cycling visibility of blocks

2009-05-26 Thread Eric Schulte
Carsten Dominik writes: > On May 25, 2009, at 10:40 PM, Sebastian Rose wrote: > >> Another good place would be inside Org-mode's core IMHO. > > I would be happy to integrate this into the core. Eric, you agree? > > - Carsten > Sounds good to me. -- Eric ___

Re: [Orgmode] Cycling visibility of blocks

2009-05-26 Thread Carsten Dominik
On May 25, 2009, at 10:40 PM, Sebastian Rose wrote: "Eric Schulte" writes: I've applied a slightly changed version of your regexp, and this is now working for all block types (the resulting file is attached). Where could this file be saved? The contrib directory seems like overkill for

Re: [Orgmode] Cycling visibility of blocks

2009-05-26 Thread Carsten Dominik
That does look cool! - Carsten On May 25, 2009, at 10:43 PM, Sebastian Rose wrote: "Eric Schulte" writes: ahh - forgot - Carsten: note the unicorns: http://cloud.github.com/downloads/SebastianRose/org-search.php/speedbar1.png :-D Sebastian Sebastian Rose writes: and use "#\\+begi

Re: [Orgmode] Cycling visibility of blocks

2009-05-25 Thread Sebastian Rose
"Eric Schulte" writes: ahh - forgot - Carsten: note the unicorns: http://cloud.github.com/downloads/SebastianRose/org-search.php/speedbar1.png :-D Sebastian > Sebastian Rose writes: > >> >> and use >> >> "#\\+begin_\\([^ ]+\\) \\(.+\\)[ \t]*\\([ >> \t]+\\([^\n]+\\)\\)?\n\\([^\000]+?\\)

Re: [Orgmode] Cycling visibility of blocks

2009-05-25 Thread Sebastian Rose
"Eric Schulte" writes: > I've applied a slightly changed version of your regexp, and this is now > working for all block types (the resulting file is attached). Where > could this file be saved? The contrib directory seems like overkill for > such a small piece of functionality maybe I should po

Re: [Orgmode] Cycling visibility of blocks

2009-05-25 Thread Eric Schulte
Sebastian Rose writes: > > and use > > "#\\+begin_\\([^ ]+\\) \\(.+\\)[ \t]*\\([ > \t]+\\([^\n]+\\)\\)?\n\\([^\000]+?\\)#\\+end_\\1" > > > :) > > > Sebastian > Hi Sebastian, Thanks for the update! I've applied a slightly changed version of your regexp, and this is now working for all bloc

Re: [Orgmode] Cycling visibility of blocks

2009-05-25 Thread Sebastian Rose
Carsten Dominik writes: > On May 25, 2009, at 3:18 AM, Sebastian Rose wrote: > >> Wow, this is great! >> >> And yes, it indeed makes sense to hide other blocks too, e.g. big ditaa >> blocks or #+BEGIN_HTML when working on LaTeX stuff (here a `S-TAB' >> action would be great, that hides all blocks

Re: [Orgmode] Cycling visibility of blocks

2009-05-25 Thread Carsten Dominik
On May 25, 2009, at 3:18 AM, Sebastian Rose wrote: Wow, this is great! And yes, it indeed makes sense to hide other blocks too, e.g. big ditaa blocks or #+BEGIN_HTML when working on LaTeX stuff (here a `S-TAB' action would be great, that hides all blocks of that sort at once). In fact, I c

Re: [Orgmode] Cycling visibility of blocks

2009-05-24 Thread emacs-orgmode
Eric Schulte writes: > The attached file should implement this feature, just load the file and > then press tab while at the beginning of a source block. Note that it > requires a newish version of org-mode which includes the > `org-tab-first-hook' variable. Very nice ! Thank you. > Maybe this

Re: [Orgmode] Cycling visibility of blocks

2009-05-24 Thread Sebastian Rose
Wow, this is great! And yes, it indeed makes sense to hide other blocks too, e.g. big ditaa blocks or #+BEGIN_HTML when working on LaTeX stuff (here a `S-TAB' action would be great, that hides all blocks of that sort at once). In fact, I changed the `org-block-hide-src-block-regexp' to "#\\+

Re: [Orgmode] Cycling visibility of blocks

2009-05-24 Thread Eric Schulte
Hi, The attached file should implement this feature, just load the file and then press tab while at the beginning of a source block. Note that it requires a newish version of org-mode which includes the `org-tab-first-hook' variable. Maybe this would make sense for all org blocks, not just src b

[Orgmode] Cycling visibility of blocks

2009-05-24 Thread emacs-orgmode
Hello, I perhaps have missed it in the manual, but, would it be possible to cycle visibility in blocks like in the example below ? #+BEGIN_something blah blah blah blah blah blah and so much blah yet to come #+END_something becomes #+BEGIN_something ... #+END_something It could help when you h