"Thomas S. Dye" writes:
> Thierry Banel writes:
>
>> You are not missing anything. MD or ORG do the job. It is just that your
>> public is made of Emacs users, and Org-mode users. So ORG sounds
>> familiar. GitHub renders pretty well ORG documents. And maybe someday
>> there will be converters f
Thierry Banel writes:
> You are not missing anything. MD or ORG do the job. It is just that your
> public is made of Emacs users, and Org-mode users. So ORG sounds
> familiar. GitHub renders pretty well ORG documents. And maybe someday
> there will be converters from ORG to INFO.
Does INFO refer
Le 15/01/2015 23:41, Phillip Lord a écrit :
> Thierry Banel writes:
>
>> Le 15/01/2015 17:11, Phillip Lord a écrit :
>> One possibility, not as good as info, but quite easy, is given by
>> GitHub. Replace your current README.md with a README.org, in org-mode
>> syntax.
> Why this replacement? md o
Alan Schmitt writes:
> I gave this a try and it works well.
>
>> Can I ask, why do you want to kill the buffer? Why not just bury it?
>
> Because otherwise I get this the next time I start lentic for the same
> file:
>
> A buffer is visiting /Users/schmitta/tmp/lentic_test.org; proceed? (y or n)
On 2015-01-15 22:28, phillip.l...@newcastle.ac.uk (Phillip Lord) writes:
> So, local variables comes *after* the ends here line. Currently, the
> "ends here" line needs to be *inside* a source block, so you would have...
>
> ;; #+begin_src emacs-lisp
> (message "foo")
> ;; #+end_src
>
> ;; #+begin
Thierry Banel writes:
> Le 15/01/2015 17:11, Phillip Lord a écrit :
I spent some time figuring out how to use it.
>> Of course, even when installed from Melpa it is self-documenting in the
>> sense that the source files are full of documentation. The lentic-org.el
>> file contains a descript
Alan Schmitt writes:
> On 2015-01-15 15:54, phillip.l...@newcastle.ac.uk (Phillip Lord) writes:
>
>> Good. If you find any examples which fail, I'd be happy to look.
>
> It's not really failing, but I don't know how to put the end of file
> markers so that lentic likes it. For instance:
>
> ;; #+
Le 15/01/2015 17:11, Phillip Lord a écrit :
>>> I spent some time figuring out how to use it.
>>>
>>> This is what I did eventually:
>>> M-xlentic-mode
>>> M-xlentic-mode ;; twice
>>> M-x lentic-mode-split-window-below
>>> Then change the new buffer to the desired mode (Java mode, C++ mode,
On 2015-01-15 15:54, phillip.l...@newcastle.ac.uk (Phillip Lord) writes:
> Good. If you find any examples which fail, I'd be happy to look.
It's not really failing, but I don't know how to put the end of file
markers so that lentic likes it. For instance:
--8<---cut here-
writes:
> Thierry Banel writes:
>
>> Nice!
>
> I also tried it and found it really interesting!
Thank you.
>
>>
>> I spent some time figuring out how to use it.
>>
>> This is what I did eventually:
>> M-xlentic-mode
>> M-xlentic-mode ;; twice
>> M-x lentic-mode-split-window-below
>> T
Alan Schmitt writes:
> On 2015-01-09 19:18, phillip.l...@newcastle.ac.uk (Phillip Lord) writes:
>
>>> I've used a similar configuration
>>>
>>> #+begin_src emacs-lisp
>>> (add-hook 'emacs-lisp-mode-hook (lambda () (setq lentic-init
>>> 'lentic-orgel-org-init)))
>>> #+end_src
>>
>> Personally, I
Thierry Banel writes:
> Nice!
I also tried it and found it really interesting!
>
> I spent some time figuring out how to use it.
>
> This is what I did eventually:
> M-xlentic-mode
> M-xlentic-mode ;; twice
> M-x lentic-mode-split-window-below
> Then change the new buffer to the desired
On 2015-01-09 19:18, phillip.l...@newcastle.ac.uk (Phillip Lord) writes:
>> I've used a similar configuration
>>
>> #+begin_src emacs-lisp
>> (add-hook 'emacs-lisp-mode-hook (lambda () (setq lentic-init
>> 'lentic-orgel-org-init)))
>> #+end_src
>
> Personally, I wouldn't do that! At the moment,
> On 2015-01-09 17:12, address@hidden (Phillip Lord) writes:
>
> > It's configurable, though. By default, the two windows share the same
> > text (which is nearly the same behaviour as indirect buffers). But they
> > can also be different (but related). I use a file or dir-local variable
> > for t
On 2015-01-09 17:12, phillip.l...@newcastle.ac.uk (Phillip Lord) writes:
> It's configurable, though. By default, the two windows share the same
> text (which is nearly the same behaviour as indirect buffers). But they
> can also be different (but related). I use a file or dir-local variable
> for
I normally do
(global-lentic-start-mode)
which just adds some keybindings for you.
Then, do one of
lentic-mode-create-in-selected-window, (C-c,h)
lentic-mode-split-window-below, (C-c,b)
lentic-mode-split-window-right (C-c,r)
Or there are menu items which does the same.
All of these create t
Nice!
I spent some time figuring out how to use it.
This is what I did eventually:
M-xlentic-mode
M-xlentic-mode ;; twice
M-x lentic-mode-split-window-below
Then change the new buffer to the desired mode (Java mode, C++ mode,
whatever).
(I was created in fundamental mode).
Is this the st
I thought some of you might be interested in the new release of my
package, lentic. One of the things that it now does is allow
multi-modal of editing of Emacs source, using org mode for the
documentation. I realise that it's already possible to use ELPA
org-babel to write literate el files, or t
18 matches
Mail list logo
