Wes Hardaker writes:
>> On Tue, 25 Aug 2009 08:30:51 -0700, Wes Hardaker
>> said:
>
>> On Tue, 25 Aug 2009 11:12:16 +0200, Carsten Dominik
>> said:
> CD> 1. Make the cursor keys LEFT and RIGHT do normal cursor motion again
>
> WH> +1. I find these two keys have confused me mo
Carsten Dominik writes:
>>> Maybe we could have something like #+XSLT: or so to configure buffer-
>>> local setting for this variable..
>>
>> Thanks for the suggestion, Carsten! It's a little hard for me to
>> decide
>> which way is better to specify the stylesheet: "#+XSLT" or "Local
>> V
Baoqiu Cui writes:
> I like %s (for stylesheets). For %p, I guess we can use it to format a
> *set* of parameters.
Yes, that's what I meant.
>> What would be cool is a way to allow the user to *add* custom spec
>> chars to the default set. (hint hint)
>
> Will we make it *too* flexible by doin
Dale Smith writes:
>>>> The current org-export-docbook-xslt-proc-command is a format string,
>>>> with a fixed order of arguments (the fo filename and then the input
>>>> docbook filname). Thats probably good enough for most (all?) xslt
>>>> pr
Baoqiu Cui writes:
>>> The current org-export-docbook-xslt-proc-command is a format string,
>>> with a fixed order of arguments (the fo filename and then the input
>>> docbook filname). Thats probably good enough for most (all?) xslt
>>> processors, but things may be more limited when it comes t
Carsten Dominik writes:
> Thanks for the suggestion, Carsten! It's a little hard for me to
>> decide
>> which way is better to specify the stylesheet: "#+XSLT" or "Local
>> Variables:". Maybe "#+XSLT" is better? I don't see many local
>> variables being used in Org mode... Please advise.
>
Greetings List,
I was suprised an pleased to discover that the docbook exporter has
the ability to apply the stylesheets to transform to fo and to also
process that to pdf. Somehing I'd like to see is a document specific
way to specify the stylesheet. I tried setting
org-export-docbook-xslt-proc
Baoqiu Cui writes:
>> This bug may be related to another I noticed. I don't yet have a clear
>> picture yet of what is (not) going on. Basically, the time reported
>> by modification time was just plain wrong. By over a day. And I
>> *know* I just saved the file.
>>
>> I'm guessing now that t
Baoqiu Cui writes:
> Thanks for reporting this bug. For some reason I missed the coverage of
> macro support in DocBook exporter, and the bug was caused by an
> "optimization" that I thought I did in the code... Variable
> org-export-opt-plist should have been set but it was not in DocBook
> ex
{{{maxro}}} expansion does not happen for docbook export until an html
export is done. After that, macros seems to be expanded properly for
docbook export.
Thanks!
-Dale
--
Dale P. Smith
da...@vtiinstruments.com
216-447-4059 x2018
216-447-8951 FAX
(Company mandated disclaimer follows...)
The
Carsten Dominik writes:
> On May 14, 2009, at 11:03 PM, Dale Smith wrote:
>
> I'm confused about the value of FORMAT in {{{date(FORMAT)}}}.
>
> I wanted to use "%B %e, %Y", but I have two problems. With the
> quotes, I get an "eval: End of file dur
Dale Smith writes:
> I'm confused about the value of FORMAT in {{{date(FORMAT)}}}.
>
> I wanted to use "%B %e, %Y", but I have two problems. With the
> quotes, I get an "eval: End of file during parsing" message. Without
> the quotes, processing
I'm confused about the value of FORMAT in {{{date(FORMAT)}}}.
I wanted to use "%B %e, %Y", but I have two problems. With the
quotes, I get an "eval: End of file during parsing" message. Without
the quotes, processing stops at the comma, expanding to "May 14"
instead of "May 14, 2009".
Thanks,
t. Thanks Baoqiu Cui.
-Dale
> From 0c534df7af71e0a742a7123a14e0293da9f0e4c6 Mon Sep 17 00:00:00 2001
From: Dale Smith
Date: Fri, 8 May 2009 10:54:49 -0400
Subject: [PATCH] Add support for docbook export for dot and ditaa blocks.
---
contrib/lisp/org-exp-blocks.el |4 ++--
1 files changed,
Carsten Dominik writes:
> On Mar 13, 2009, at 3:05 AM, Baoqiu Cui wrote:
>
>> Baoqiu Cui writes:
>>
>>> Dale Smith writes:
>>>
>>>> Somthing that muse has that I'd really like to see in org is some
>>>> way to insert raw doc
Baoqiu Cui writes:
> I just posted the code for DocBook exporter to Google Code.
I've been enjoying this docbook exporter for sveral days now. Thanks
Baoqiu!
Somthing that muse has that I'd really like to see in org is some way
to insert raw docbook into the exported output. The LaTeX exporter
Sebastian Rose writes:
> Gour writes:
>> Otoh, number of tags in DocBook is overwhelming and, imgo, way too
>> distracting for most documentation tasks, at least, for *my* use-cases.
>
>
> It is, and that's exactly why the DocBook export is such a great thing.
>
> You could say a similar thing
Sebastian Rose writes:
> The LaTeX and XHTML export (which, by the
> way, could be transformed just as good as docbook) work and are widely
> used.
I'm not sure sure. I think docbook is much more content oriented than
LaTeX and xhtml, which seem to be more presentation oriented. To
me anyway.
Baoqiu Cui writes:
> The only thing that is missing (at least to me) in current Org-mode is
> the exporter for DocBook format.
There is quite a bit of similarity between org and muse formats. I've
found that I can edit .muse files in org-mode and stiil publish to
docbook.
> During the last we
Ken Harris writes:
> On my keyboard layout, I can hit all of C-u, C-a, C-e, C-p,
> C-k, and C-y with my left hand, so I can a whole lot of simple
> navigation editing without putting down the mouse (or mousing back
> over to my emacs window).
Wow. Big hands!
-Dlae
--
Dale P. Smith
da...@vxite
David Thole writes:
> I'd be interested in finding this out as well. Could you provide details
> Dale on how you got it to import correctly into Diary even? There's a
> huge disconnect right now for me between my calendar and what I do my GTD
> stuff in.
Sure. I have
(add-hook 'gnus-articl
Howdy list,
My company recently moved to an exchange server (ugh!) and so now i've
been getting icalendar meeting requests. I have
icalendar-import-buffer in my gnus-article-prepare-hook, and that
works well enough to add things to my diary. Diary entries show up im
my appointemts, so that's goo
"Rob Weir" <[EMAIL PROTECTED]> writes:
> On 13 Aug 2008, Robert Miesen wrote:
>> I've noticed that as I go through tasks listed in my agenda, it's
>> very easy to select and operate on the wrong task because it's too
>> easy to loose track of what task I am operating on. If the entire task
>> line
Bastien <[EMAIL PROTECTED]> writes:
> Dale Smith <[EMAIL PROTECTED]> writes:
>
>> I just noticed there is an article on org-mode in the December Linux
>> Journal by Abhijeet Chavan.
>
> Great. Any chance that people in this list could read it *somewhere*,
>
I didn't see this here yet. Sorry if I'm being redundant. (again?)
I just noticed there is an article on org-mode in the December Linux
Journal by Abhijeet Chavan.
Yaayy. Nice job, Abhijeet.
-Dale
--
Dale P. Smith
[EMAIL PROTECTED]
216-447-4059
216-447-8951 FAX
___
Carsten Dominik <[EMAIL PROTECTED]> writes:
> I am releasing Org-mode 5.01. It is available at my website
>
> http://www.astro.uva.nl/~dominik/Tools/org
>
> and also through Emacs CVS.
>
> I am pretty excited about this release, a new major version.
Wow! What a lot of new functionality. I
Dale Smith <[EMAIL PROTECTED]> writes:
> What I'm really asking is a way to extend the current list of link
> types (gnus:, file:, vm:, etc.) with some user-defined types.
How about an alist of (type . replacement), with string as simple
string replacement, and maybe a funct
i?id=1234][Bug# 1234]], but
that's a lot to type in. Hmm. It wouldn't be too hard to whip up
some elist that generates a link like that.
What I'm really asking is a way to extend the current list of link
types (gnus:, file:, vm:, etc.) with some user-defined types.
> On Sep 22, 200
I've been trying out org-mode instead of planner-el for a few weeks now. I like
it. However, there are a few things I miss. One is how easy it was to ad my
own
hyperlink types. This was all I needed to add Bugzilla:: links:
(setq muse-wiki-interwiki-alist
'(("Bugzilla" . "http://10.1.2.
I'm using org-mode 1.48 and a locally installed (in my $HOME) gnus 5.10.6 and
emacs 21.3.1 (whatever is on a FC3 box). When I C-c l in an *Article* buffer,
I get this backtrace:
Debugger entered--Lisp error: (invalid-function (macro . #[(&optional number)
"xx" [number gnus-data-header gnu
30 matches
Mail list logo
