I'm noticing something with mobile org and wonder if others have the same
experience.
An item that is in the Agenda View is truncated (only first 10 lines shown)
when viewed under the "Agenda views..." selector, but that same item when
viewed in its actual .org file is complete.
I don't see wh
(defun comment-org-in-src-block ()
(interactive)
(org-edit-special)
(mark-whole-buffer)
(comment-dwim nil)
(org-edit-src-exit))
;)
Xebar Saram writes:
> wow wonderful!
> this works flawlessly when i select the region inside the code block and
> run the command.
> I wonder if any lisp w
Ken Mankoff writes:
> Hi Joakim,
>
> On 2015-06-26 at 07:45, joa...@verona.se wrote:
>> I'm writing a manuscript for a publisher. The process looks like:
>>
>> - I write a chapter in org mode, export it to odt
>>
>> - I apply the styles the publisher wants to use with a libreoffice
>> macro. Th
wow wonderful!
this works flawlessly when i select the region inside the code block and
run the command.
I wonder if any lisp wizards out there can modify Johns code and make it
auto select all lines *inside* the current block and then comment it? could
be useful to other people i assume.
thx agai
Hi Joakim,
On 2015-06-26 at 07:45, joa...@verona.se wrote:
> I'm writing a manuscript for a publisher. The process looks like:
>
> - I write a chapter in org mode, export it to odt
>
> - I apply the styles the publisher wants to use with a libreoffice
> macro. This isn't particularily efficient,
joa...@verona.se writes:
> I'm writing a manuscript for a publisher. The process looks like:
>
> - I write a chapter in org mode, export it to odt
>
> - I apply the styles the publisher wants to use with a libreoffice
> macro. This isn't particularily efficient, but I failed at modifying
> ox-
You need:
% -*- mode:bibtex; eval: (bibtex-set-dialect 'biblatex); -*-
You probably have to close and reopen the file, and you will probably be
prompted for running local variables (or use C-x C-e after the command
above it
With this, it works fine for me.
This isn't really an org-ref problem,
This seems to work for some toy examples:
(defun comment-org-in-src-block ()
(interactive)
(org-edit-special)
(comment-dwim nil)
(org-edit-src-exit))
Xebar Saram writes:
> Hi all
>
> i was wondering if anyone knew of a command or bind to quickly comment the
> entire content of an org code b
Alan Schmitt writes:
> On 2015-06-27 12:07, Alan Schmitt writes:
>
>> No, and I can reproduce this with an empty configuration. So I guess
>> there is something fishy going on in the generation of the temporary org
>> file.
>
> Here is an ECM to show the issue. Evaluate this code:
>
> #+begin_sr
On 2015-06-27 12:07, Alan Schmitt writes:
> No, and I can reproduce this with an empty configuration. So I guess
> there is something fishy going on in the generation of the temporary org
> file.
Here is an ECM to show the issue. Evaluate this code:
#+begin_src emacs-lisp
(org-export-define-der
Dear John,
On Fri, 26-06-2015, at 22:58, John Kitchin wrote:
> You could have multiple file fields I suppose, and adapt [1] to give you
> a choice of which one to open.
That is an intriguing suggestion. I'll try to play with it.
>
> Personally, I have one pdf per bibtex entry, named by the key
On 2015-06-26 17:36, Nicolas Goaziou writes:
> Hello,
>
> Alan Schmitt writes:
>
>> Is there any reason why the options would disappear during export?
>
> Maybe "ox-pandoc" doesn't handle this meta-data.
ox-pandoc does not do anything with that meta-data when generating the
temporary org file.
Hi all
i was wondering if anyone knew of a command or bind to quickly comment the
entire content of an org code block (with the correct comment syntax)?
thx!
Z
13 matches
Mail list logo
