Thank you for your quick reply, Thorsten.
Yes, as I mentioned, and as you noticed, the HTML export does not seem
to work correctly for the last case. The #BEGIN_SRC and #END_SRC
delimiters are exported literally.
--
Omid
Sent from my Emacs
On 10/15/2013 10:53 PM, Thorsten Jolitz wrote:
>
> PS:
PS:
Omid writes:
> When exporting to HTML (Org mode version 8.2.1 ELPA; GNU Emacs version
> 24.3.1) I see the a strange behavior which can be reproduced with the
> following minimal example:
>
> This exports correctly
> #+BEGIN_SRC sh
> ls
> #+END_SRC
>
> - This also exports correctly
> #+
Omid writes:
> - This does NOT export correctly (code block is not detected)
> #+BEGIN_SRC sh
> ls
> #+END_SRC
>
> Is there any way around this behavior without removing the indentation
> for the code block delimiters?
I think the 'official'regexp to detect a src-block starts like this
,---
Suvayu Ali writes:
> I can try debugging org-grep, but I don't know where I should start.
I would either step through org-grep (using C-u C-M-x first over any
line of the org-grep definition within org-grep.el, or add (message ...)
lines within the function before to later check the *Messages* b
Hello All,
When exporting to HTML (Org mode version 8.2.1 ELPA; GNU Emacs version
24.3.1) I see the a strange behavior which can be reproduced with the
following minimal example:
This exports correctly
#+BEGIN_SRC sh
ls
#+END_SRC
- This also exports correctly
#+BEGIN_SRC sh
ls
#+END_SRC
- T
James Harkins writes:
> I don't want to drag it out much further as it's well off topic,
I'm sorry that my little grammar question, in the P.S. of the original
message, generated all that traffic. I did not know the answers were so
debatable, and was rather expecting a quick and conclusive repl
hi all,
apologies for breaking the threading as I just subscribed to the list
and thanks for trying out ZShaolin :^)
I am happy to see some of the experts here find it useful. The Emacs
included in my APK is "experimental" and so far comes without elisp
files, which you can add from your own c
Thanks! That's a huge productivity gain for me.
Although, I don't see "q" buries it in the buffer.
On Tue, Oct 15, 2013 at 10:35 PM, Carsten Dominik
wrote:
> Both "q" and "x" do this. "q" just buries the buffer, "x" will also kill
> the buffer.
>
> - Carste
>
> On Oct 15, 2013, at 1:15 PM, Chr
Dnia 2013-10-15, o godz. 02:11:53
Rasmus napisał(a):
> Hi Xavier,
>
> Xavier Garrido writes:
>
> But you have to be certain that this command is present.
>
> You could use etoolbox to test it. That brings in another dependency,
> tho.
Not really.
\providecommand{\email}[1]{whatever you lik
Hi Michael,
thank you for the reminder, sorry for the delay.
The patch has been applied now.
- Carsten
On Oct 15, 2013, at 4:46 PM, Michael Brand wrote:
> Hi Carsten, Bastien and Nicolas
>
> On Tue, Oct 8, 2013 at 9:40 AM, Michael Brand
> wrote:
>> On Mon, Sep 30, 2013 at 8:35 PM, Michael B
Both "q" and "x" do this. "q" just buries the buffer, "x" will also kill the
buffer.
- Carste
On Oct 15, 2013, at 1:15 PM, Chris Henderson wrote:
> I use C-c a m to search tags. How do I close this window when I'm done? At
> the moment, I'm using C-x k to kill this window, C-c o to jump to m
Eric,
Eric S Fraga writes:
> Rasmus writes:
>
>> Hi Org-list,
>>
>> How do you guys manage repeated irregular entries when using
>> org-caldav?
>
> I use a different heading for each event so I never have multiple
> timestamps within a given section. So I can't help you directly with
> your pr
Rasmus writes:
> #+begin_src emacs-lisp
> (defun rasmus/condtionally-remove-label (headline backend info)
> "condtionally remove label"
> (if (and
> (org-export-derived-backend-p backend 'beamer)
> (string-match "[.*?allowframebreaks.*?]" headline))
> (replace-
Rasmus writes:
> Hi Org-list,
>
> How do you guys manage repeated irregular entries when using
> org-caldav?
I use a different heading for each event so I never have multiple
timestamps within a given section. So I can't help you directly with
your problem.
However, note that MobileOrg also do
Eric S Fraga writes:
> A better solution would be to have a variable to be able to customise
> this behaviour, I imagine.
Why? Labels are /usually/ completely harmless. Please open a bug
report at Beamer's Bitbucket.
–Rasmus
--
I hear there's rumors on the, uh, Internets. . .
Eric S Fraga writes:
> Hello,
>
> technically, I guess this is a bug in beamer and not in org's
> exporter. However, if I specify the =allowframebreaks= option for a
> frame, the exporter generates the following LaTeX code on beamer export:
>
> \begin{frame}[allowframebreaks,label=sec-1-1-1]{S
Eric S Fraga writes:
[...]
> The question is: how can I tell the exporter to *not* generate label=
> directives? I have no need for these and, at the moment, I am having to
> edit the LaTeX source to get my slides done.
I found some time to look at the code and it appears that the automatic
cr
On 8.10.2013, at 12:36, Scot Becker wrote:
> Just a quick note to say that it's possible to get a full Emacs+org-mode on
> (unrooted) Android using an app called 'zshaolin'. You can either download
> the app from the Google Play store for approx $3 or download the toolchain
> and source from
Hello,
technically, I guess this is a bug in beamer and not in org's
exporter. However, if I specify the =allowframebreaks= option for a
frame, the exporter generates the following LaTeX code on beamer export:
\begin{frame}[allowframebreaks,label=sec-1-1-1]{Some definitions}
The "label=sec-1-
Hi all,
Pressing these key-chords just gives:
user-error: To use shift-selection with Org-mode, customize
`org-support-shift-select'
I don't think that it's very productive to occupy a key binding with a
function that
just says to me that I made an error. Or is it an advertisement for
shift-sele
Hi Carsten, Bastien and Nicolas
On Tue, Oct 8, 2013 at 9:40 AM, Michael Brand
wrote:
> On Mon, Sep 30, 2013 at 8:35 PM, Michael Brand
> wrote:
>> For the use case of org-table-transpose-table-at-point there, I made a
>> patch for org-table-transpose-table-at-point to preserve indentation
>> and
On Tue, Oct 15, 2013 at 4:04 AM, Sebastien Vauban
wrote:
>
>
That is a nice feature I had forgotten about!
When I export your snippet to html I get this:
This file was exported on .
The answer to 2 + 3 is .
Is there some trick to make them evaluate? Probably I have set a variable
in org-mod
Chris Henderson writes:
> I use C-c a m to search tags. How do I close this window when I'm done? At
> the moment, I'm using C-x k to kill this window, C-c o to jump to my org
> file and then C-x 1 make the window full screen.
>
> Is there any other way to close the tags window?
Will 'q' work?
I use C-c a m to search tags. How do I close this window when I'm done? At
the moment, I'm using C-x k to kill this window, C-c o to jump to my org
file and then C-x 1 make the window full screen.
Is there any other way to close the tags window?
Thanks.
On Mon, Oct 14, 2013 at 07:50:36PM -0400, François Pinard wrote:
> Suvayu Ali writes:
>
> >> > No matter what I search for, I get 0 results!
> > I'm on Linux.
>
> Hmph! As it works nicely for me, I thought it would be useful to
> others. I'm saddened it does not work for you. How could we pro
Eric Schulte writes:
[...]
> I actually get a different error [1], namely that the call line can't be
> parsed because we're using a regex to grab call lines and regular
> expressions can't count parens.
Ah, okay, this makes sense. My example was contrived so this is not a
problem for me.
> E
Rainer Stengele writes:
[...]
> Thank you Eric,
> until now TODOs for me always seemed to be a bit heavyweight because of the
> headline needed.
> I wonder how people are working.
> Do you use checkboxes a lot or prefer TODOs even for simple subtasks?
Yes, I use headlines for all tasks, no mat
Hello John,
John Kitchin wrote:
> I implemented a version of elisp links to dynamically generated content at
> export time here:
> http://jkitchin.github.io/blog/2013/10/14/Lisp-links-in-org-mode-to-dynamically-generated-content/
>
> I am not sure it was you are thinking about, but maybe it could
28 matches
Mail list logo
