Achim Gratz wrote
> The question really is if org hasn't evolved to the point where it needs
> a more general quoting/escaping mechanism.
+1
However there's caveat:
Just run
zgrep '' *.el.gz
on your emacs' el.gz files and you will find that its not empty -- So
general and conven
Bernt Hansen writes:
[...]
> Could you provide a sample clock report using this patch to get a
> better idea of why you find this useful?
Yes, here you are, along with the contents of a sample file, so that you
may get a gist of my need for inheritance.
* Clocktables
#+BEGIN: clocktable :max
Hi,
I was trying to configure the above variable for some overlay
environments in org-beamer. I saw a few of the default environments use
the %x format but I couldn't find any documentation about what it does.
From the exported latex file it seems a \label{somelabel} tag is
inserted. Attached is a
Hi Orgers,
I wanted to insert comments in the exported tex file for latex export.
Is there an standard way to do that? I found normal '%text' gets
exported as '\%text'. However I can export comments by putting
'%%text', it gets exported as '%\%text'.
Is there any other solutions out there?
--
S
Puneeth
> Attached is a patch that allows having lists, tables, blockquotes and
> other org blocks in footnotes. Source code blocks still don't work.
>
Would you mind posting an example test case that covers all the above
cases. I am trying to merge my branch with the most recent changes in
th
This is slightly out of thread.
I pulled the master branch with an intention to "re-baseline" my branch
and I saw some 37 lines were changed since I "branched" out my odt
branch. My heart just sinked.
A request from my side. Would it be possible to delay adding of new
capabilities and features t
Hi Jambunathan,
Jambunathan K writes:
> I pulled the master branch with an intention to "re-baseline" my branch
> and I saw some 37 lines were changed since I "branched" out my odt
> branch. My heart just sinked.
>
> A request from my side. Would it be possible to delay adding of new
> capabilit
Niels Giesen writes:
> Bernt Hansen writes:
>
> [...]
>
>> Could you provide a sample clock report using this patch to get a
>> better idea of why you find this useful?
>
> Yes, here you are, along with the contents of a sample file, so that you
> may get a gist of my need for inheritance.
>
> *
Dear list,
When asking for an agenda view (C-c a), org mode opens all files in
the agenda list in individual buffers. I keep lots of files in my
list (one per project), so having all those buffers open each time I
visit my agenda is pretty annoying. Is there a way to make org mode
not open each
Dear all,
Another fanatical Org-mode convert new to the list. Following the
'advice' of [1] I am attempting to generate my personal website using
Org publishing, but I'm running up against a pretty weird bug when I try
to export inline images. The code gets rendered so that the HTML
appears in t
Julian Burgos writes:
> Dear list,
>
> When asking for an agenda view (C-c a), org mode opens all files in
> the agenda list in individual buffers. I keep lots of files in my
> list (one per project), so having all those buffers open each time I
> visit my agenda is pretty annoying. Is there a
Sean Whitton writes:
> Another fanatical Org-mode convert new to the list. Following the
> 'advice' of [1] I am attempting to generate my personal website using
> Org publishing, but I'm running up against a pretty weird bug when I try
> to export inline images. The code gets rendered so that t
On 27 Mar 2011, Bernt Hansen wrote:
> Julian Burgos writes:
>
>> Dear list,
>>
>> When asking for an agenda view (C-c a), org mode opens all files in
>> the agenda list in individual buffers. I keep lots of files in my
>> list (one per project), so having all those buffers open each time I
>> vis
Thanks. Using x is good enough for now. I´ll explore also Michael´s
suggestions. It would be good to have the agenda open in a buffer
without having all the agenda files opened too.
On Sun, Mar 27, 2011 at 2:21 PM, Michael Markert
wrote:
> On 27 Mar 2011, Bernt Hansen wrote:
>> Julian Burgos
Hi,
When I'm using orgmode to write out largish documents, I often run into
the outlining problem that it's apparently not possible to continue
text of a higher level outline once subsections have been started.
A simplified example of such an outline would be:
---
* Main headline
Some though
> ---
> * Main headline
> Some thoughts expressed here
>
> ** Subheading 1
>More thoughts expressed here
> ** Subheading 2
>More thoughts expressed here
>
> I would like to have this text part of 'Main headline', not of
> 'Subheading 2'
>
Why is copy pasting not an option ...
You can't do that, as it would be akin to trying to have in a book
Section 1
Stuff
Section 1.1.1
More stuff
Now this goes under Section 1
Not really an idiom that makes sense (I find its best to think of
org-mode's headings as chapter headers
What you can do is something like the following:
*
On zo 27-mrt-2011 16:52
Cian wrote:
> You can't do that, as it would be akin to trying to have in a book
>
> Section 1
> Stuff
> Section 1.1.1
> More stuff
>
> Now this goes under Section 1
>
> Not really an idiom that makes sense (I find its best to think of
> org-mode's headings as chapter
Aloha Suvayu,
I'd be inclined to use #+LaTeX: %text
Alternatively (and perhaps more robustly with multiline comments) you
could make certain to \usepackage{verbatim} and then use
#+BEGIN_COMMENT
text
#+END_COMMENT
following the example of block level markup here:
http://orgmode.org/worg/org
Marcel van der Boom wrote:
> When writing I tend to think about org headings as 'handles' to a
> logical block of information, including its child blocks. Apparently my
> analogy clashes with what org-mode wants. I had my hopes on a
> customization option.
>
> Is there a strong reason this coul
I agree with Marcel on this. If org is supposed to help get /to/ the
final version of a document, then it should support the (possibly
inconsistent) structures that can appear in all the in-between steps
after conceiving of the document and before the final version.
The workaround I use is to use
On Mar 27, 2011, at 6:45 AM, Nick Dokos wrote:
Marcel van der Boom wrote:
When writing I tend to think about org headings as 'handles' to a
logical block of information, including its child blocks.
Apparently my
analogy clashes with what org-mode wants. I had my hopes on a
customization o
Marcel wrote:
> When I'm using orgmode to write out largish documents, I often run into
> the outlining problem that it's apparently not possible to continue
> text of a higher level outline once subsections have been started.
Here's a not-so-pretty hack to get what (I guess) you want
Marcel van der Boom writes:
> On zo 27-mrt-2011 16:52
> Cian wrote:
>
>> You can't do that, as it would be akin to trying to have in a book
>>
>> Section 1
>> Stuff
>> Section 1.1.1
>> More stuff
>>
>> Now this goes under Section 1
>>
>> Not really an idiom that makes sense (I find its best t
Hello,
"Filippo A. Salustri" writes:
> The workaround I use is to use lists instead of headlines. The
> problem then becomes the extra work of turning lists into
> headines+text later.
What about using C-c C-* on the list?
Regards,
--
Nicolas
It seems to me we're getting into some real design territory here, in
that it comes down to a question of a "proper" outline.
I agree that a proper outline is such that Marcel's format is "improper."
I agree that org follows the proper outline, was designed to suit it,
and therefore it isn't surpri
Yes, of course. But it's still something *I* have to do as a separate
task. This breaks my cognitive workflow; it's a distraction. One of
the reasons I use org is that it's so distraction-free compared to
every other tool I've tried. It seems like distraction-freeness is a
big deal in org, so I
"Filippo A. Salustri" writes:
> It seems to me we're getting into some real design territory here, in
> that it comes down to a question of a "proper" outline.
> I agree that a proper outline is such that Marcel's format is "improper."
> I agree that org follows the proper outline, was designed t
Out of my depth too. That's why I'd be happy to live with it as is. :)
Cheers.
Fil
On 27 March 2011 13:18, William Gardella wrote:
> "Filippo A. Salustri" writes:
>
>> It seems to me we're getting into some real design territory here, in
>> that it comes down to a question of a "proper" outline
Hullo,
On Sun, Mar 27, 2011 at 22:32, William Gardella wrote:
> Marcel van der Boom writes:
>
>> On zo 27-mrt-2011 16:52
>> Cian wrote:
>>
>>> You can't do that, as it would be akin to trying to have in a book
>>>
>>> Section 1
>>> Stuff
>>> Section 1.1.1
>>> More stuff
>>>
>>> Now this goes un
On Sun, Mar 27, 2011 at 8:21 PM, Julian Burgos wrote:
> Thanks. Using x is good enough for now. I´ll explore also Michael´s
> suggestions. It would be good to have the agenda open in a buffer
> without having all the agenda files opened too.
>
Following code should do what you want (I think).
IIUC the goal is to allow continuing body text. Is this for org
itself or for export? Or both?
I wonder if inline tasks can be used to achieve some of this.
Samuel
--
The Kafka Pandemic:
http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html
I support t
I wonder if org should export ASCII tables using tabs.
If I send to this list, I can be confident that everybody will know to
display in a monospace font. That is not true for non-technical
audiences. Yet I think there are times when I want to send ASCII
instead of HTML. At least, I am not conf
That is indeed an excellent solution if you want to add a tag for a
todo kw. However, I wonder if there is a direct approach, where the
exporter simply does not export if it is a certain todo kw. Is the
solution to have the exporter delete anything with that todo kw? Or
is there a way to have it
If I could I would refactor org-clock-put-overlay into a function that
puts overlays on the current headline but I am not able to do so.
Wouldn't blocks that allowed org headings offer this. If I understand
this correctly, what you're really looking for is the ability to mark
certain bits of text as one blob, so that you can move them around
easily as you draft a paper, without worrying about pulling other bits
of the paper. So this
Hi Tom,
On Sun, 27 Mar 2011 06:36:18 -1000
"Thomas S. Dye" wrote:
> Aloha Suvayu,
>
> I'd be inclined to use #+LaTeX: %text
>
> Alternatively (and perhaps more robustly with multiline comments)
> you could make certain to \usepackage{verbatim} and then use
>
> #+BEGIN_COMMENT
> text
> #+END_C
On Sun, Mar 27, 2011 at 2:37 PM, Samuel Wales wrote:
> That is indeed an excellent solution if you want to add a tag for a
> todo kw. However, I wonder if there is a direct approach, where the
> exporter simply does not export if it is a certain todo kw. Is the
> solution to have the exporter de
William Gardella writes:
> I think org-mode should aim to be flexible enough to accomodate all
> writers, writing tasks, and writing styles.
With flexibility comes complexity, which runs counter to "org should be
simple".
> Maybe for this particular issue it would be enough to give org-mode
> a
Achim Gratz wrote:
> The question really is if org hasn't evolved to the point where it needs
> a more general quoting/escaping mechanism. This might be one of the
> things to ponder during the upcoming exporter cleanup, but goes a bit
> beyond just exporting.
>
Absolutely right - org has grow
Achim Gratz writes:
> William Gardella writes:
>> I think org-mode should aim to be flexible enough to accomodate all
>> writers, writing tasks, and writing styles.
>
> With flexibility comes complexity, which runs counter to "org should be
> simple".
>
Agreed, but I'd say org is already one of
Marcel van der Boom writes:
> On zo 27-mrt-2011 16:52
> Cian wrote:
>
>> You can't do that, as it would be akin to trying to have in a book
>>
>> Section 1
>> Stuff
>> Section 1.1.1
>> More stuff
>>
>> Now this goes under Section 1
>>
>> Not really an idiom that makes sense (I find its best t
I agree that this is important.
For new features, Extensible Syntax (capitalized because it is a
specific proposal for a concrete universal syntax) allows you to use
the same quoting, escaping, nesting, exporting, etc. solutions that
were arrived at as a one-time fundamental mechanism.
This reduc
Marcel van der Boom writes:
[...]
> I've looked for documentation or customization options on this, but
> haven't found any yet. What I have done so far is turn the subheadings
> into lists or surround them by *bold markers*, which helps a little.
Seems to me to be worth an entry in the FAQ, isn'
Perhaps we could have a tag like :noexport: except that it exports
body. It does not export the header. Optionally, it would be
replaced with a blank line.
Then he can put headers anywhere he wants.
Would this work for the OP's use case?
I'm not certain, but I don't think it's possible to solve the OP's
problem in LaTeX.
Tom
On Mar 27, 2011, at 3:07 PM, Samuel Wales wrote:
Perhaps we could have a tag like :noexport: except that it exports
body. It does not export the header. Optionally, it would be
replaced with a blank li
46 matches
Mail list logo
