Nick Dokos writes:
> One machine is running Gnus v. 5.13: that one smooshes the code
> blocks together.
>
> The other is running Ma Gnus v. 0.12: that one leaves empty
> lines between blocks.
Do they both fontify blocks ?
--
Nico.
Nick Dokos writes:
> Sebastien Vauban
> writes:
>
>> Nick Dokos wrote:
>>> Thorsten Jolitz writes:
Thorsten Jolitz writes:
As a side-remark, I did send these blocks with emptly lines between them,
and when I look at my post in gmane the format looks alright, however
wh
Ernesto Durante writes:
> Thierry Banel writes:
>
>> Le 15/08/2014 19:22, Ernesto Durante a écrit :
>>
>> True.
>> And to achieve that the :includes header tag was added:
>> #+BEGIN_SRC C++ :includes
>>
>> (Because otherwise a #include statement would end up in the main() function)
>>
>> For me
Hi Ernesto,
This looks like a good change and I'd like to apply it. Could you
re-submit this commit after doing the following.
1. ensure no lines go beyond 80 characters in length
2. remove all lines which include only closing parens
(such lines are generally considered bad lisp style)
3. com
Ernesto Durante writes:
> Thierry Banel writes:
>
>>> I have identified a minor bug. When a source code block has the mode
>>> cpp, we cannot expand the code or more precisely the code is not
>>> expanded in the correct way because the following function is missing
>>>
>>> (defun org-babel-exp
Hello,
I am following the instructions here:
http://stackoverflow.com/questions/20164918/
But I am configuring org-modules to use the checklist module.
Except it doesn't work.
I've verified that my config has been updated to show that the
checklist module should be loaded.
How do I debug this
My apologies for the ambiguity. I am happy with the way the block itself
exports. I have a document with many such blocks interspersed throughout
the document. I wanted to create an org document which contains just
these blocks, and then export that document to .tex.
E.g., if I had a paper, I wou
I have posted this to StackOverflow, if someone wants to grab the karma:
http://stackoverflow.com/questions/25437069/
On 18 August 2014 02:52, Noah Slater wrote:
> Hello,
>
> I have a number of habits set up that I regularly fill in the day
> after the activity was done. Is there a way to mark a
Hi Tory,
You’re right...I inadvertently tested the proposed solution with the
latex backend, but it turns out there’s a small difference between how
the latex and beamer backends calculate their \author. I think both
backends should behave identically here and that the latex behavior is
more corr
Hey Aaron,
THat's a good idea but it doesn't quite work; looks like #+LATEX_HEADER stuff
is put in BEFORE the author nil, so I just end up with \author{} to trump my
author. I've tried rearranging things but it doesn't seem to effect it.
- Tory
Aaron Ecay writes:
> Hi Tory,
>
> It looks li
Hi Tory,
It looks like having a short and long author isn’t supported by the
beamer exporter out of the box. Your best bet is probably to add this
line to the top of your org file to turn off the automatic generation
and insertion of \author by the export template:
#+OPTIONS: author:nil
Then, y
My Beamer presentation needs the following:
\author[short-author]{Really long author}
Emphasis on the [short-author] parameter. I've been through the manual but I
don't see a way to accomplish this sort of thing with export (there are other
fields that do something similar, too). S
Thorsten Jolitz writes:
> Rasmus writes:
>
> Hi Rasmus,
>
>> Thorsten Jolitz writes:
>>
>>> As a side-remark, I did send these blocks with emptly lines between them,
>>> and when I look at my post in gmane the format looks alright, however
>>> when I open it in gnus the empty lines are gone and
Rasmus writes:
Hi Rasmus,
> Thorsten Jolitz writes:
>
>> As a side-remark, I did send these blocks with emptly lines between them,
>> and when I look at my post in gmane the format looks alright, however
>> when I open it in gnus the empty lines are gone and it looks like this:
>
> Do you by an
Rasmus writes:
> Thorsten Jolitz writes:
>
>> As a side-remark, I did send these blocks with emptly lines between them,
>> and when I look at my post in gmane the format looks alright, however
>> when I open it in gnus the empty lines are gone and it looks like this:
>
> Do you by any chance hav
Hi Thorsten,
Thorsten Jolitz writes:
> As a side-remark, I did send these blocks with emptly lines between them,
> and when I look at my post in gmane the format looks alright, however
> when I open it in gnus the empty lines are gone and it looks like this:
Do you by any chance have `gnus-arti
Le 20/08/2014 22:40, Ernesto Durante a
écrit :
Another question if you allow me ?
Looking at code in Ob-C you transform a table/list variable in a C array
of char*. Should it not be std::wstring ? some unicode string ?
Best Ernesto
Absolutely!
Un
"Stephen J. Barr" writes:
> I have a document that has a lot of definitions defined as custom
> blocks, eg.
>
> #+LABEL: defn:my-great-definition
> #+ATTR_LATEX: :options [My Great Definition]
> #+begin_definition
> Blah blah.
> #+end_definition
>
>
> Would it be possible
I have a document that has a lot of definitions defined as custom
blocks, eg.
#+LABEL: defn:my-great-definition
#+ATTR_LATEX: :options [My Great Definition]
#+begin_definition
Blah blah.
#+end_definition
Would it be possible to export to .tex a file that has all of the
d
On Thursday, 21 Aug 2014 at 14:28, avigoz wrote:
> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen. You don't know how to make a good report? See
>
> http://orgmode.org/manual/Feedback.html#Feedback
>
> Your bug report will be posted to the Or
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
-
Nicolas Goaziou writes:
> Hello,
>
> Thorsten Jolitz writes:
>
>> Ok, thanks, that sounds promising. OTOH, is the use of "\\S-" really
>> mandatory,
>
> No, it isn't.
>
>> couldn't a more robust construct be used, either something
>> like this (untested) regexp:
>>
>> ,
>> | "[^[:space:]\\n]
Hello,
torys.ander...@gmail.com (Tory S. Anderson) writes:
> I have a shell function that exports my agenda to an ical file and
> uploads it for Google to read; however, there seem to be a couple
> glaring omissions from the ical. Here's the bash line that works over
> my agenda for export:
>
>
Hello,
Ken Mankoff writes:
> I've turn on Markdown exporting with (require 'ox-md). Citations aren't
> being exported properly, so I'm trying to customize it. I have the
> following setup:
>
> (org-add-link-type
> "textcite" (lambda (key) (org-open-file cby-references-file t nil key))
> (lamb
Hello,
Thorsten Jolitz writes:
> Ok, thanks, that sounds promising. OTOH, is the use of "\\S-" really
> mandatory,
No, it isn't.
> couldn't a more robust construct be used, either something
> like this (untested) regexp:
>
> ,
> | "[^[:space:]\\n]+"
> `
AFAIK, [:space:] is not compati
25 matches
Mail list logo
