On Nov 13, 2010, at 4:43 PM, Nick Dokos wrote:
Carsten Dominik wrote:
I have just added the last command missing names to the manual. So
if =20=
you compile the manual in the latest git version, you will find =20
command names listed for almost all keys listed in the manual,
along =20
At Fri, 12 Nov 2010 23:50:35 -0600,
Carsten Dominik wrote:
>
> Hi David,
>
> On Nov 12, 2010, at 11:01 PM, David Abrahams wrote:
>
> >
> > Hi Carsten,
> >
> > I'm sorry to belabor this, but I'm a little confused about what you're
> > saying.
>
> that is because I just talked garbage.
I don't t
At Sat, 13 Nov 2010 11:25:25 +0530,
Anupam Sengupta wrote:
>
> > David Abrahams writes:
>
> > Is it merely the autoload of org-capture-templates, or is this a
> > general rule for everything in org-install? I think I'm perfectly
> > happy to work with the dependency in place as long as it's
Hi Dov,
That is correct, there is no method of highlighting inline code blocks,
the begin_src constructs are just for evaluation of inline code.
You can customized the `org-babel-default-inline-header-args' to inhibit
the execution of inline code blocks on export.
Best -- Eric
Dov Grobgeld wri
Hi
With the org-info-js mode enabled each section is shown as a seperate page,
but then I would like to get current page marked in the TOC in some way
(e.g. class=current and then some CSS to make the markup) ... but is it
possible?
/Benny
___
Emacs-org
Chao LU writes:
> I'm trying to generating the agenda file everyday as a pdf file, then
> print it out. But I failed to modify org-mode to do so automatically
> under windows system, each time I have to get the agenda generated
> first, then manually M-x ps-spool-buffer-with-faces, to save it as
At Sat, 13 Nov 2010 07:18:42 +0100,
Vincent Belaïche wrote:
>
> Herein attached follows my patch. Please feel free for brickbats...
>
Could I ask you to resend the patch in a format that can be applied
with Git? E.g. try:
git diff > my-new-patch.patch
Best,
-- David
--
OpenPGP... 0x99ADB83
Evening,
I have spent an hour looking around for how to define blockquotes in org-mode.
So far I have seen discussion but nothing in terms of how you actually define
them. Is this still a future feature or is there a way to do this already?
Thanks
'Mash
___
On 2010-11-14 23:32+0530, Puneeth wrote:
> Hi 'Mash,
>
> On Sun, Nov 14, 2010 at 11:23 PM, 'Mash wrote:
> > Evening,
> >
> > I have spent an hour looking around for how to define blockquotes in
> > org-mode. So far I have seen discussion but nothing in terms of how you
> > actually define them.
At Thu, 04 Nov 2010 14:33:32 +0100,
Jean-Marie Gaillourdet wrote:
> A file with #+STARTUP: indent isn't syntax highlighted at all. The
> message buffer says fontification fails with: (invalid-function
> with-silent-modifications)
>
> All calls to =with-silent-modifcations= have been introduced by g
At Sun, 7 Nov 2010 05:52:23 + (UTC),
Anupam Sengupta wrote:
> This allows the `org-capture-templates' saved in the separate emacs-custom.el
> file to be correctly loaded. Note that this behavior is from 7.02/7.3, and
> probably has to do with the custom-autoload definition of this variable in
Hi 'Mash,
On Sun, Nov 14, 2010 at 11:23 PM, 'Mash wrote:
> Evening,
>
> I have spent an hour looking around for how to define blockquotes in
> org-mode. So far I have seen discussion but nothing in terms of how you
> actually define them. Is this still a future feature or is there a way to do
At Mon, 08 Nov 2010 09:45:25 -0500,
Nick Dokos wrote:
> Something to do with the compilation of the org-babel-map-src-blocks
> macro, no doubt. I don't see it with uncompiled files.
Not a solution, but some debugging showed that
`org-babel-get-src-block-info' fails to get the info of the source
b
At Fri, 29 Oct 2010 19:24:32 -0400,
Marvin Doyley wrote:
>
> [1 ]
> [1.1 ]
> Does anybody have a function that turns a org header into file with a link
> to the file where it originated from ?
> For example, lets say I have the following heading
>
> * Apples
> * Cherry
> * Tomatoes
>
> Lets say I
Aloha all,
The LaTeX exporter passes over #+BEGIN_EXAMPLE blocks. In the
following example, "Absent" does not make it into the .tex file, but
"Present" does. I'm expecting the #+BEGIN_EXAMPLE block to appear in
the .tex file wrapped in a verbatim environment.
--- cut here --
Thomas S. Dye wrote:
> Aloha all,
>
> The LaTeX exporter passes over #+BEGIN_EXAMPLE blocks. In the
> following example, "Absent" does not make it into the .tex file, but
> "Present" does. I'm expecting the #+BEGIN_EXAMPLE block to appear in
> the .tex file wrapped in a verbatim environment.
>
Ok. Thanks for clarifying it. The documentation isn't clear on this issue.
Regards,
Dov
On Sun, Nov 14, 2010 at 18:03, Eric Schulte wrote:
> Hi Dov,
>
> That is correct, there is no method of highlighting inline code blocks,
> the begin_src constructs are just for evaluation of inline code.
>
>
Nick Dokos writes:
> Thomas S. Dye wrote:
>
>> "Present" does. I'm expecting the #+BEGIN_EXAMPLE block to appear in
>> the .tex file wrapped in a verbatim environment.
>>
>> --- cut here
>> * Export LaTeX examples
>> #+BEGIN_EXAMPLE
>> Absent
>> #+END_EXAMPLE
>>
>> : Pres
Hi,
Only partly.
On 11/14/10 12:24 AM, Sébastien Vauban wrote:
Hello,
A quick (but not easy?) question about the Org publish to HTML and CSS: I
would like to make the 3 different timestamps stand out with different
backgrounds.
Is it possible with CSS? I have the impression that it currently
Christian Moe wrote:
> Hi,
>
> Only partly.
>
> On 11/14/10 12:24 AM, Sébastien Vauban wrote:
> > Hello,
> >
> > A quick (but not easy?) question about the Org publish to HTML and CSS: I
> > would like to make the 3 different timestamps stand out with different
> > backgrounds.
> >
> > Is it po
Aloha Nick and Bernt,
Thanks for looking into this. It looks like I've broken something.
All the best,
Tom
On Nov 14, 2010, at 10:34 AM, Bernt Hansen wrote:
Nick Dokos writes:
Thomas S. Dye wrote:
"Present" does. I'm expecting the #+BEGIN_EXAMPLE block to appear
in
the .tex file wra
At Sun, 14 Nov 2010 15:56:20 -0500,
Nick Dokos wrote:
> Perhaps it'd be possible to (optionally) add an "id" selector to the timestamp
> elements and use that for CSS manipulation, tied to an org-mode ID or
> some other unique id? Or perhaps just postprocess the HTML output to add such
> ids.
Or
I reviewed the org-manual for capture, and noticed that we don't have
a way to specify tab stops. I use yasnippet all the time to enter
information, and I can tab from field to field.
Can capture do the same?
Here's an example from yasnippet:
--
23 matches
Mail list logo
