Samuel Wales writes:
Hi Samuel,
>> If you structure your Emacs Lisp files the 'outshine way', you can
>> convert them into complete Org files fast and easily using 'outorg.el'.
> With what I am talking about, you can:
>
> - put your Org notes in your main Org agenda files exactly where you wa
Alexander Vorobiev writes:
Hi Alexander,
> A while back I wrote a macro (based on the advice in
> http://stackoverflow.com/a/2494384/973603) which allows to activate
> minor mode bindings when a condition is true and fall back to previous
> bindings otherwise:
I just pushed a new version of o
Alexander Vorobiev writes:
Hi Alexander,
> First of all, thank you for the tutorial and the code! Outshine has become
> a major component of my workflow, I use it in all my source code buffers (sql,
> R, elisp).
Thanks, I use it in all my elisp and PicoLisp buffers too, and I'm happy
that it w
First of all, thank you for the tutorial and the code! Outshine has become
a major component of my workflow, I use it in all my source code buffers
(sql, R, elisp).
I have one question/proposal regarding key bindings. Outshine binds TAB
to outshine-cycle-subtree which only does something useful (c
Hi Eric,
Here is old not-working not-finished code that I abandoned. But it
illustrates the goal.
Samuel
===
Maybe something like:
- In source file, C-c ' to go to Org entry associated with nearest ID marker
- C-u C-c ' to create ID marker and create its Org entry in your Org file
Hi Thorsten,
On 4/12/13, Thorsten Jolitz wrote:
> If you structure your Emacs Lisp files the 'outshine way', you can
> convert them into complete Org files fast and easily using 'outorg.el'.
No, we are talking about different things.
With what I am talking about, you can:
- put your Org note
Samuel Wales writes:
> On 4/5/13, Thorsten Jolitz wrote:
>> that sounds like a different idea. I have heard about programming
>> environments that keep comments and source-code in two different (but
>> sync'd) files to minimize distraction from the source code - maybe a
>> possible use case for
On 4/5/13, Thorsten Jolitz wrote:
> that sounds like a different idea. I have heard about programming
> environments that keep comments and source-code in two different (but
> sync'd) files to minimize distraction from the source code - maybe a
> possible use case for your idea?
Yes. The purpose
On 4/6/13, Eric Schulte wrote:
>>> The idea is to be in my-lisp.el, and do C-c ', and get to a canonical
>>> entry in my-org.org, then do C-c ' again and get back to my-lisp.el.
> That could be handy. For jumping back and for by function name, the
> following simple implementation might be suffi
Eric Schulte writes:
> That could be handy.
Indeed! Nice hack to add to Worg, or even to contrib/?
Don't hesitate to spread the word :)
--
Bastien
Thorsten Jolitz writes:
> Samuel Wales writes:
>
> Hi Samuel,
>
>> IIUC, I don't think this is related. The idea is not to edit source
>> code in Org buffers, and it is not to use a Navi buffer or to do
>> navigation.
>>
>> The idea is to be in my-lisp.el, and do C-c ', and get to a canonic
Samuel Wales writes:
Hi Samuel,
> IIUC, I don't think this is related. The idea is not to edit source
> code in Org buffers, and it is not to use a Navi buffer or to do
> navigation.
>
> The idea is to be in my-lisp.el, and do C-c ', and get to a canonical
> entry in my-org.org, then do C-c
Hi Thorsten,
IIUC, I don't think this is related. The idea is not to edit source
code in Org buffers, and it is not to use a Navi buffer or to do
navigation.
The idea is to be in my-lisp.el, and do C-c ', and get to a canonical
entry in my-org.org, then do C-c ' again and get back to my-lisp.el.
Samuel Wales writes:
> Great write-up, Thorsten.
thanks
> There is a whole other set of options also. I don't know if they are
> close enough for you to include, but it's worth pointing them out.
>
> These are in the general category of Org annotations. Instead of
> editing Org in a temporary
Great write-up, Thorsten.
There is a whole other set of options also. I don't know if they are
close enough for you to include, but it's worth pointing them out.
These are in the general category of Org annotations. Instead of
editing Org in a temporary buffer, you use a real, permanent Org fil
Aloha Thorsten,
What a joy to find the following bit on Worg!
To sum it up in one sentence: Outline with Outshine outshines
Outline
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
16 matches
Mail list logo
