Thanks all for your responses, let me clarify a bit . . .
First of all I need <#+OPTIONS: \n:t> because when I export an org file
which has song lyrics in it I want to preserve the lines but accept css
for nice printing (and singing afterwards).
Regarding, the other question, that of exporti
Hello
> First of all I need <#+OPTIONS: \n:t> because when I export an org
> file which has song lyrics in it I want to preserve the lines but
> accept css for nice printing (and singing afterwards).
Can you give an example of an org file, the html export as it is today,
the html export as you
Hi Gregory
"Sullivan, Gregory (US SSA)" writes:
> Appended is a patch with a couple of small changes to
> org-taskjuggler.el, addressing the following issues:
Thanks for your patch.
> General:
>
> * in org-taskjuggler-open-project, the duration is never calculated
> (default is always used).
You just need BEGIN_VERSE ... END_VERSE instead of _QUOTE.
cm
On 4/5/11 9:31 AM, katepano wrote:
Actually it is very simple . . . it misses the at the end of
the lines
check the attachments (the song is in greek but I think will give you
the idea)
Katepano
On 04/05/2011 10:18 AM, Jambunathan
thanks for the tip, this is true, but not entirely the same . . .
Katepano
On 04/05/2011 10:52 AM, Christian Moe wrote:
You just need BEGIN_VERSE ... END_VERSE instead of _QUOTE.
cm
On 4/5/11 9:31 AM, katepano wrote:
Actually it is very simple . . . it misses the at the end of
the lines
chec
Dear katepano,
as you can see, it has taken 11 emails on a high volume email list
to get the answer to your simple question. More than 1100 people have
subscribed to this mailing list, an unknown number of people
read it on aggregators like gmane. That is a lot of time and energy
spent unnecessa
On Apr 5, 2011, at 9:56 AM, katepano wrote:
> thanks for the tip, this is true, but not entirely the same . . .
In what way is it not the same? Of cause it is not the same because it
does preserve line breaks. Why do you not like this solution as much?
I would argue that in fact it is a *much
Dear Dominik.
I see your point and it is accepted, of course. I admit, I should write
my email more clearly. Anyway, thanks for your time.
On the other hand I really would like to see #+OPTIONS: \n:t working, if
this possible and do not cause much frustration.
thanks anyway
Katepano
On 04/
On Apr 5, 2011, at 10:15 AM, katepano wrote:
> Dear Dominik.
> I see your point and it is accepted, of course. I admit, I should write my
> email more clearly. Anyway, thanks for your time.
>
> On the other hand I really would like to see #+OPTIONS: \n:t working, if this
> possible and do not
Nick Dokos hp.com> writes:
> If you download an org distribution (through git or a tar file or what
> have you), you should be able to find the doc/org.texi file which is
> used to generate the manual.
Found it. In debian it's gzipped and located in /usr/share/doc/org-mode/ where
I found both o
Christian Egli writes:
>> * in org-taskjuggler-open-project, the duration is never calculated
>> (default is always used).
>
> Good catch and thanks for your patch. Unfortunately the patch causes
> problems with my export. The duration is now correctly calculated,
> however the root task now also
Hi Aankhen,
Aankhen wrote:
> 2011/4/4 Sébastien Vauban :
>> [snip]
>>
>> 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.
>> - acronyms :: idem.
>>
>> Maybe those sh
I guess my use case is pretty common: I use org-agenda to keep track of
appointments, and use org-agenda-skip-scheduled-if-done to avoid
displaying past appointments. If I want to review what I did last week
for instance, I'd like the SCHEDULED dates to appear in
org-agenda-log-mode, not the dates
Hi,
I've been wondering about this for a bit. It would make things a bit
more consistent for me if all properties are in the 'properties'-drawer.
Or am I missing something here?
marcel
--
Marcel van der Boom -- http://hsdev.com/mvdb.vcf
HS-Development BV-- http://www.hsdev.com
So! web appl
Marcel van der Boom writes:
> I've been wondering about this for a bit. It would make things a bit
> more consistent for me if all properties are in the 'properties'-drawer.
> Or am I missing something here?
The main reason I can think of is that this is historical. CLOSED: was
invented long be
Let me summarize the steps I carried out eventually, to use the package
manager. Note, I am using emacs 23 based editor which was shipped with org-mode
6.33.
* Updating
Follow the steps:
** Intsall the package manager
*** Download the =packages.el= file from
http://repo.or.cz/w/emacs.git/blob_pl
This looks like it may be a multidisciplinary problem, but this
mailing list has provided good solutions for these things in the past,
so I figured it would be the first place to check.
I've been exporting latex documents via org-mode, but I noticed that
the editing mode (after C-c ') was LaTeX mo
05/04/11 17:37, Chris Beard
> This looks like it may be a multidisciplinary problem, but this
> mailing list has provided good solutions for these things in the past,
> so I figured it would be the first place to check.
>
> I've been exporting latex documents via org-mode, but I noticed that
> the
On Tue, Apr 5, 2011 at 4:52 PM, Bernt Hansen wrote:
> Marcel van der Boom writes:
>
> > I've been wondering about this for a bit. It would make things a bit
> > more consistent for me if all properties are in the 'properties'-drawer.
> > Or am I missing something here?
>
> The main reason I can
[Noch ein mal: I forgot to copy the list. Apologies... to Izzie in
particular who is receiving multiple instances. At least, I edited
this version down a bit.]
Izzie wrote:
> ...
> I was hoping org mode documentation had been made with org mode, I wasn't
> expecting a texi file format I had not
On 05/04/11 16:31, Dror Atariah wrote:
Let me summarize the steps I carried out eventually, to use the package
manager. Note, I am using emacs 23 based editor which was shipped with org-mode
6.33.
* Updating
Follow the steps:
** Intsall the package manager
*** Download the =packages.el= file f
Hi all
For many use cases I would like one of both opposites:
1) the option to have e. g. CLOSED: as :CLOSED: in a drawer and on its
own line as mentioned before
2) the option to have e. g. :CATEGORY: without any drawer, like:
* holidays
:CATEGORY: holiday
** xmas
<2011-12-25 Sun>
** new yea
"Eric Schulte" writes:
>>
>
> Thanks for catching this, I've just pushed up a fix for this issue. The
> column headers were being lost during the export processing.
>
>>
>>
>> Also if I use :cache yes header. The html export recomputes the block.
>> Wouldn't it be reasonable to have the exporter
I have just discovered org-babel supports ocaml and I've just started to
learn it. My problem is when appending two lists together, when run
through org-babel returns a error message. I would try and run this
code
[3;2;3] @ [3;2;3;4;5];;
and get a error message saying
"Invalid function: 3"
Is
Hi Sébastien,
2011/4/5 Sébastien Vauban :
> Aankhen wrote:
>> [snip]
>> Acronyms are natively supported in HTML. That is all.
>
> Thanks for reporting this. Wasn't aware of it. Though, that does not alter the
> need (at least, what I consider so) for acronyms handling in/from Org.
>
> Let's clarif
Aankhen writes:
[...]
> Thank you for the clarifications. I’m going to talk a bit more about
> HTML as that’s where I have the most experience. I am in agreement
> with you when you say that builtin support for acronyms would be
> useful (although I feel it would be good to generalize it to
>
Hi all
The items 2 and 4 in the following example are not shown in the agenda
with today's release_7.5-135-g7021f70.
Question about item 2: Is this a bug since the items 1 and 3 are shown?
Question about item 4: The user manual tells that %% must start at the
first column. What would be required
Hello,
When returning results from a postgresql database, if the first value is
NULL then no results are returned.
Versions: orgmode git commit c01c2ad Fri Mar 18, postgresql 9.0.3.
This works as expected:
#+begin_src sql :engine postgresql :cmdline -d postgres
SELECT 1 as A, NULL as B;
#+end_s
Hi Eric, Aankhen and al.,
Just answering very quickly on one sole idea of the exchanged ones in this
thread:
Eric S Fraga wrote:
> Aankhen writes:
>> The expansion is invisible by default; it shows up in a tooltip when you
>> hover over the text. You can try a live example to see for yourself.[1
On Wed, Apr 6, 2011 at 00:57, Eric S Fraga wrote:
> Aankhen writes:
>
> [...]
>
>> Thank you for the clarifications. I’m going to talk a bit more about
>> HTML as that’s where I have the most experience. I am in agreement
>> with you when you say that builtin support for acronyms would be
>> us
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.
-
Steps to reproduce:
Include an entry like this in your org-capture-templates:
("t" "Todo" entry (file+headline "~/org/gtd.org" "Tasks")
"* TODO %?\n %i\n %a")
Now, delete everything in ~/org/gtd.org except for a lone "Tasks" headline.
Put point on the next line, and start a capture wi
I've just stumbled across what I regard as a bug in the html export of
description list items.
The problem has to do with whether the specification of a description
list includes a trailing space or not; i.e., whether "- Item ::" is
treated the same way as "- Item :: ". LaTeX export treats these
Ethan Ligon are.berkeley.edu> writes:
>
> I've just stumbled across what I regard as a bug in the html export of
> description list items.
>
> The problem has to do with whether the specification of a description
> list includes a trailing space or not; i.e., whether "- Item ::" is
> treated the
Thomas Jack wrote:
> Steps to reproduce:
>
> Include an entry like this in your org-capture-templates:
> ("t" "Todo" entry (file+headline "~/org/gtd.org" "Tasks")
> "* TODO %?\n %i\n %a")
>
> Now, delete everything in ~/org/gtd.org except for a lone "Tasks" headline.
>
> Put point o
Hi,
When exporting to LaTeX/PDF and using org-mode markup for italics
inside quotation marks, the /'s are getting left alone. So...
,---
| /word/
`---
works fine, but
,---
| He said, "/word/"
`---
Does not.
Any suggestions on this? I could convert everything to \emph{}, but
that makes for ugl
Hi,
One thing I really like to use orgmode for is research. Lately,
there's a mass of stuff on-line that I've been reading though and am
about to start reading through a series of articles and had the idea
to yank them into org for "inline notes."
My current experiment has been:
- wget the websi
Hi,
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
`---
I didn't know that. I say that perhaps it's obvious, because I guess
when the toc does show up, it's format is:
,---
|
I'd like my page1 to be on a separate page from the TOC. How do I
insert a pagebreak to do this? If I do it here:
,---
| * Section 1
| \newpage
| test in section 1
`---
I get the TOC, then the Section 1 title, then a page break, and then the text.
Thanks!
John
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 only problem I've run into is have a
lot to say in an inline
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...
Using the following code, you can control whether notes
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 only problem I've run into is hav
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.
On 04/05/2011 10:32 PM, Eric Schulte wrote:
Hi John,
Interesting use case, I definitely see the utility. I think that blocks
may be an appropriate solu
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.
If the thing to be annotated is read-only, I have other ideas.
Samuel
--
The Kafka Pandemic:
http://thekafkapandemic.
John Hendy writes:
> Hi,
>
>
> 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
> `---
> Anyway, if these two are necessary, perhaps the manual could be
> updated (
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 notes...
#+begin_src css
blockquote {
border-left: 1px s
John Hendy wrote:
> I'd like my page1 to be on a separate page from the TOC. How do I
> insert a pagebreak to do this? If I do it here:
> ,---
> | * Section 1
> | \newpage
> | test in section 1
> `---
>
> I get the TOC, then the Section 1 title, then a page break, and then the text.
>
>
Assumi
47 matches
Mail list logo
