Hi,
Is anyone out there willing to give me private org mode support / advice
consultation? I can pay via pay pal, personal check in the mail or am open
to other payment forms.
Here is the ideal person:
- very familiar with org-mode
- low hourly rate
- able to view my desktop remotely
- famili
Hi Philip,
thank you for this very detailed report and recipe.
First of all, the date tree target currently is meant only
for entry-type captures. If you use a plain capture type,
it will go to the end of the buffer and the localization
by the date tree is ignored.
I can see that it might be ni
Hi,
When you want to resize an inline image, you have to write something like the
following:
--8<---cut here---start->8---
#+ATTR_HTML: width=50%
[[./images/toto.png]]
--8<---cut here---end--->8---
This generates the followi
Jambunathan K wrote:
> [1. text/plain]
> Exporting the below table to LaTeX throws an error. Let me know if you
> need any additional info.
> [2. text/x-verbatim]
> *** Table.el Table with no Spanning
> +---+---+
> |Term |Percentage |
> +--
* lisp/org-latex.el (org-export-latex-convert-table.el-table): Fix
format-string for insertion of captions.
This fixes a bug introduced in caa5da1 since when the caption itself
is not placed inside the caption command.
---
lisp/org-latex.el |2 +-
1 files changed, 1 insertions(+), 1 deletions
On Wed, Apr 6, 2011 at 10:18, Jambunathan K wrote:
> John Hendy writes:
> [snip]
>> Maybe this is obvious to most, but I was puzzled by it. It seems that
>> ,---
>> | #+options: toc:t
>> `---
>>
>> will not function when paired with:
>> ,---
>> | #+options: toc:t num:nil
>> `---
> [snip]
>
> Is t
Jambunathan K writes:
Hi, Jambunathan,
> Exporting the below table to LaTeX throws an error. Let me know if you
> need any additional info.
>
>
> *** Table.el Table with no Spanning
> +---+---+
> |Term |Percentage |
> +---+---
On di 05-apr-2011 10:52
Bernt Hansen wrote:
> I don't think there should be a requirement for having
> a drawer when you mark a task done just to record the CLOSED date.
> Having an option to enable this behaviour would be fine with me.
Agreed, such an option would be welcomed by me too obvious
Hi Jeff,
Jeff Horn wrote:
> Have you tried using org-inline-task without a TODO keyword? These
> super-deep "headlines" aren't treated as headlines, so they don't
> break doc structure, but they are foldable, and unlike COMMENT keyword
> headlines, they're printable.
I second this approach, and a
Carsten Dominik writes:
Thanks Carsten,
> I can see that it might be nice to simply add some text
> under the date headline in a date tree, in order to build
> up a long journal entry from little snippets.
Yes, this is exactly what I do over the course of the day and I find it
very useful. The
On Apr 6, 2011, at 12:50 PM, Philip Rooke wrote:
> Carsten Dominik writes:
>
> Thanks Carsten,
>
>> I can see that it might be nice to simply add some text
>> under the date headline in a date tree, in order to build
>> up a long journal entry from little snippets.
>
> Yes, this is exactly wh
On Apr 6, 2011, at 12:50 PM, Philip Rooke wrote:
> Carsten Dominik writes:
>
> Thanks Carsten,
>
>> I can see that it might be nice to simply add some text
>> under the date headline in a date tree, in order to build
>> up a long journal entry from little snippets.
>
> Yes, this is exactly wh
An html export of:
#+BEGIN_SRC org
I am [[http://example.org][so *ERRATICALLY* /excited/ about this *LINK*]]
#+END_SRC
Results in:
I am http://example.org";>so ERRATICALLY
excited about this LINK
Whereas it *should* result in:
I am http://example.org";>so ERRATICALLY excit
2011/4/5 Eric Schulte :
> Hi John,
>
> Interesting use case, I definitely see the utility. I think that blocks
> may be an appropriate solution, for example if you enclose your notes in
> "notes" blocks, then it should be easy to control whether or not they
> are exported...
Definitely a candidat
On Tue, Apr 5, 2011 at 11:10 PM, Erik Iverson wrote:
> If you export to HTML, you should be able to export your notes with a CSS
> class to style your notes as differently from the text as you like.
Great idea. Unfortunately, I'm almost entirely a LaTeX -> PDF guy.
Though, if I ever wanted blog i
On Tue, Apr 5, 2011 at 11:14 PM, Samuel Wales wrote:
> I agree this is interesting.
>
> Another option is an annotation mechanism with unbreakable
> bidirectional links -- ID markers work for this. You can stick the
> markers anywhere.
Heck yes -- this sounds *awesome*. Could you give an example
On Wed, Apr 6, 2011 at 12:02 AM, Eric Schulte wrote:
> Erik Iverson writes:
>
>> If you export to HTML, you should be able to export your notes with a
>> CSS class to style your notes as differently from the text as you
>> like.
>>
>
> I like the following for offsetting quotes, may work well for
On Tue, Apr 5, 2011 at 10:21 PM, Jeff Horn wrote:
> Have you tried using org-inline-task without a TODO keyword? These
> super-deep "headlines" aren't treated as headlines, so they don't
> break doc structure, but they are foldable, and unlike COMMENT keyword
> headlines, they're printable. The on
On Wed, Apr 6, 2011 at 4:20 AM, Aankhen wrote:
> On Wed, Apr 6, 2011 at 10:18, Jambunathan K wrote:
>> John Hendy writes:
>> [snip]
>>> Maybe this is obvious to most, but I was puzzled by it. It seems that
>>> ,---
>>> | #+options: toc:t
>>> `---
>>>
>>> will not function when paired with:
>>> ,
>>
>> Using the following code, you can control whether notes enclosed in
>> "notes" blcks will be exported by changing the value of the
>> *export-my-notes* variable, when it is nil your notes will not be
>> exported, when t they will be exported as quoted text.
>>
>> #+begin_src emacs-lisp
>> (d
On Wed, Apr 6, 2011 at 11:33 AM, John Hendy wrote:
> On Tue, Apr 5, 2011 at 10:21 PM, Jeff Horn wrote:
>> Have you tried using org-inline-task without a TODO keyword? These
>> super-deep "headlines" aren't treated as headlines, so they don't
>> break doc structure, but they are foldable, and unli
Hi all
In the meantime I realized that for a good stability of the document
consistency it is a rather bad idea to have the name of a parent
heading like `Bach' to be part of the key to the item `Prelude' for
the [[*Bach/Prelude]] link mentioned earlier. Therefore I will instead
use :ID: links wit
Hi John,
They only solve half of the problem.
Unbreakable bidirectional links using ID markers would solve
the teleport problem. Both ends can be moved anyplace,
including inside stretches of text. They are a little like
a generalization of footnotes. They use org IDs. You can
specify various
Christopher Allan Webber writes:
> An html export of:
>
> #+BEGIN_SRC org
> I am [[http://example.org][so *ERRATICALLY* /excited/ about this *LINK*]]
> #+END_SRC
>
> Results in:
>
> I am http://example.org";>so ERRATICALLY
> excited about this LINK
>
> Whereas it *should* res
Hi,
Just stumbled across something very odd I can't figure out. Here's a sample:
,-
| #+OPTIONS: toc:t TeX:t LaTeX:t H:4 f:t todo:nil num:t tags:nil
| #+latex_class: article
|
| * Section
| 1. *A section*: a bunch of text is here and it seems like the
footnote is doing
| something odd. [f
On Wed, Apr 6, 2011 at 12:27 PM, Samuel Wales wrote:
> Hi John,
>
> They only solve half of the problem.
>
> Unbreakable bidirectional links using ID markers would solve
> the teleport problem. Both ends can be moved anyplace,
> including inside stretches of text. They are a little like
> a gene
Hi John,
On 2011-04-06, John Hendy wrote:
> This sounds very cool. I can't gather from the mailing list thread
> (which appears to be just you) whether this is implemented or just
> suggested. Is it possible to actually use this or not?
Others have commented on it. Can't find links for you now.
On Wed, Apr 6, 2011 at 1:16 PM, Samuel Wales wrote:
> Hi John,
>
> On 2011-04-06, John Hendy wrote:
>> This sounds very cool. I can't gather from the mailing list thread
>> (which appears to be just you) whether this is implemented or just
>> suggested. Is it possible to actually use this or not?
Hello,
John Hendy writes:
> Just stumbled across something very odd I can't figure out. Here's a sample:
> ,-
> | #+OPTIONS: toc:t TeX:t LaTeX:t H:4 f:t todo:nil num:t tags:nil
> | #+latex_class: article
> |
> | * Section
> | 1. *A section*: a bunch of text is here and it seems like the
>
Sébastien Vauban
writes:
>
> When discussing exporters and features, two things that come up to my
> mind as missing as a "general Org feature":
>
> - bibliography :: works for LaTeX[1], not for HTML export.
Have you tried the contributed module org-exp-bibtex.el? It is not a
self-contained org-m
On 4/6/2011 9:33 AM, John Hendy wrote:
> ...
Inline comments already look pretty good, and I can do something like this:
,-
| *** Notes
| Here's some notes just want to see how this looks. Here's some notes
just want to see
| how this looks.
|
| Here's some notes just want to see
Hi Matt,
Matt Lundin wrote:
> Sébastien Vauban writes:
>>
>> When discussing exporters and features, two things that come up to my mind
>> as missing as a "general Org feature":
>>
>> - bibliography :: works for LaTeX[1], not for HTML export.
>
> Have you tried the contributed module org-exp-bibte
On Tue, Apr 5, 2011 at 8:20 PM, Nick Dokos wrote:
> Yes, I can. What version of emacs are you using?
>
> Mine is: GNU Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version
> 2.22.0) of 2011-03-16. I'll update
Thanks! Glad it's not just me.
I'm all the way back on "GNU Emacs 23.1.1 (x86_64-pc-l
Thomas Jack wrote:
> On Tue, Apr 5, 2011 at 8:20 PM, Nick Dokos wrote:
> > Yes, I can. What version of emacs are you using?
> >
> > Mine is: GNU Emacs 24.0.50.1 (x86_64-unknown-linux-gnu, GTK+ Version
> > 2.22.0) of 2011-03-16. I'll update
>
> Thanks! Glad it's not just me.
Not me: I'd be glad
I cant really give too many details or suggestions as to why it failed,
but the default xml string at the top of export to html files was
causing apache to fail.
,
| Parse error: syntax error, unexpected T_STRING in
| /home/shamrock/common-files/webs/richardriley.net/projects/emacs/index.html
On Wed, Apr 6, 2011 at 12:33 PM, John Hendy wrote:
> So... if I were just interested in my notes (say I wanted to just push
> the notes to my blog or share them without all the other text), it
> might get odd to see all of those headlines. Can one export just the
> text and hide the headline text
On Wed, Apr 6, 2011 at 1:33 PM, Nicolas Goaziou wrote:
> Hello,
>
> John Hendy writes:
>
>> Just stumbled across something very odd I can't figure out. Here's a sample:
>> ,-
>> | #+OPTIONS: toc:t TeX:t LaTeX:t H:4 f:t todo:nil num:t tags:nil
>> | #+latex_class: article
>> |
>> | * Section
Richard Riley wrote:
>
> I cant really give too many details or suggestions as to why it failed,
> but the default xml string at the top of export to html files was
> causing apache to fail.
>
> ,
> | Parse error: syntax error, unexpected T_STRING in
> | /home/shamrock/common-files/webs/ric
I'm new to org-mode but would like to use it for preparing docs for
latex and html. This works perfectly from within emacs (aquamacs,
actually). I would like to have a way to export a file to html from
the command-line so that I can potentially include and org-to-html
filter for my static website
org-publish-cache-ctime-of-src tries (but does not always succeed) to
deal with symlinks: file-symlink-p returns the target as a string, but
if the target is relative to the symlink, that's not going to fly.
e.g. if c is a symlink like this
/a/b/c->../d/f
then (file-symlink-p "/a/b/c") -> "..
Sean Davis writes:
> I would like to have a way to export a file to html from the
> command-line
,[ C-h f org-export-as-html-batch RET ]
| org-export-as-html-batch is a compiled Lisp function in `org-html.el'.
|
| (org-export-as-html-batch)
|
| Call the function `org-export-as-html'.
| Thi
Nick Dokos wrote:
> ...It also
> needs to treat the case of a non-existent symlink target (where
> file-symlink-p returns t).
>
Scratch that: in that case, it gets the file attributes of the
symlink itself, so no problem.
42 matches
Mail list logo
