> On 06-May-2015, at 9:44 pm, Ken Mankoff wrote:
>
>
> Recent update means you have to put it in a macro...
>
> #+TITLE: Foo @@latex:\\@@ Bar
>
> Or:
> #+MACRO: NEWLINE @@latex:\\@@ @@html:@@
> #+TITLE: Foo {{{NEWLINE}}} Bar
>
> https://emacs.stackexchange.com/questions/255/new-line-in-title
Hello,
Leo Ufimtsev writes:
> If I have a list with colons like:
>
> - List a ::
> Cheese
> Bannana
> - List b ::
> Pineapples
> Tomatoes
>
> If I then select the entire list and call org-toggle-headings, then I would
> *expect* this:
>
> * List a
> Cheese
> Bannana
> * List
Hello,
Rasmus writes:
> Actually, the error you found is more interesting than what I first
> though, as any link with anchors will trigger the error, it seems.
> org-publish-cache must be non-nil, which seems to linger on publishing a
> project.
Correct. External references can only be solved
Rasmus writes:
> I guess that's fine. Still, someone who never uses narrows may find jump
> better, especially for short documents. If the org-src window can be
> configured to show less than a fullscreen I guess I would have no concerns
> with this proposal.
I pushed a different approach. C-c
Hello,
Rasmus writes:
> Vikas Rawal writes:
>
>> Isn’t \\ in headlines expected to cause a line break?
>
> (member 'line-break (org-element-restriction 'headline)) => nil
>
> I don't know the rational.
Because, in Org, line breaks can only happen at the end of line, and
headlines are only 1
On 2015-05-06 Wed 03:24, Rasmus wrote:
> Hi Titus,
>
> Titus von der Malsburg writes:
>
>> Parentheses are punctuation, so the $ in my example should be
>> interpreted as math delimiters. I think whoever wrote the code, simply
>> overlooked parentheses when implementing the punctuation part.
>
>
Hello Nicolas,
Nicolas Goaziou writes:
[... 77 lines omitted ...]
> I hope this clarifies the purpose of the change.
It does. Thank you very much for taking the time.
[... 41 lines omitted ...]
>> Are you still planning on throwing warnings or errors in the event of
>> duplicate or invalid
Vikas Rawal writes:
> Isn’t \\ in headlines expected to cause a line break?
(member 'line-break (org-element-restriction 'headline)) => nil
I don't know the rational.
—Rasmus
--
May the Force be with you
Ken Mankoff writes:
> Or:
> #+MACRO: NEWLINE @@latex:\\@@ @@html:@@
> #+TITLE: Foo {{{NEWLINE}}} Bar
For some instances of "foo" and "bar", this may be a nicer solution:
#+title: foo
#+subtitle: bar
--
. . . The proofs are technical in nature and provides no real understanding
Recent update means you have to put it in a macro...
#+TITLE: Foo @@latex:\\@@ Bar
Or:
#+MACRO: NEWLINE @@latex:\\@@ @@html:@@
#+TITLE: Foo {{{NEWLINE}}} Bar
https://emacs.stackexchange.com/questions/255/new-line-in-title-of-an-org-mode-exported-html-document
-k.
On 2015-05-06 at 07:58, Vik
Isn’t \\ in headlines expected to cause a line break?
It gets exported in LaTeX to $\backslash$
Is this intended behaviour?
Thanks,
Vikas
Is there a task defined for this work?
I am interested in this too.
Grant Rettke
--
g...@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it serious
Matt Price writes:
>> I guess it should, but I don't know the rational for the always-centering
>> of headers. . . If we imposed that change headlines of tables with no
>> instructions would no longer be centered as they default to the "left"
>> class. This could be an issue if this is a good d
Rainer M Krug writes:
>> What do you expect?
>>
>> Should the "::*SOMETHING"-part be discarded without warning?
>
> Well - the ideal solution would be a warning (or error message) with a
> reference to the link. At the moment, a link to a non existing file is
> exported, a link to a section in a
Hello,
If I have a list with colons like:
- List a ::
Cheese
Bannana
- List b ::
Pineapples
Tomatoes
If I then select the entire list and call org-toggle-headings, then I would
*expect* this:
* List a
Cheese
Bannana
* List b
Pineapples
Tomatoes
But instead the first
On May 6, 2015 06:57, "Rasmus" wrote:
>
> Jay Belanger writes:
>
> > When I looked at the resulting html, it looked fine:
> > Math Department
> > But then I checked the css code, which is given by the value of
> > `org-html-style-default' in ox-html.el:
> >
> > th.right { text-align: cente
On 2015-05-06 at 06:28, Rasmus wrote:
> Paul Harper writes:
>
>> he other thing is in the end I have to convert from the .tex file to a
>> .docx file using pandoc
>
> Org exports to odt via ox-odt. You can presumably export directly to docx
> using org-odt-convert-processes.
Although I recomme
Rasmus writes:
> Hi,
>
> Rainer M Krug writes:
>
>> more info and a reproducible example:
>>
>> when exporting the following org file
>>
>> * A link to a non existent file
>> [[file:~/NONEXISTENT.org::*SOMETHING][Link to header in non existing org
>> file]]
>
> What do you expect?
>
> Should t
Is there any way to correlate between the position in an org-mode buffer
and an export from that buffer. So, if I have
* Header
With some text
Exported to
Header
With some text
I want do be able to match between the position of the "W" in "with"
between the two buffers?
Phil
Jay Belanger writes:
> When I looked at the resulting html, it looked fine:
> Math Department
> But then I checked the css code, which is given by the value of
> `org-html-style-default' in ox-html.el:
>
> th.right { text-align: center; }
> th.left { text-align: center; }
> th.ce
Hi,
Rainer M Krug writes:
> more info and a reproducible example:
>
> when exporting the following org file
>
> * A link to a non existent file
> [[file:~/NONEXISTENT.org::*SOMETHING][Link to header in non existing org
> file]]
What do you expect?
Should the "::*SOMETHING"-part be discarded
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.
-
I was trying to get table elements to align left when exported to html,
and I was having a bit of trouble doing it. I had a table entry
at the top
||
in the appropriate column, but that wasn't working.
When I looked at the resulting html, it looked fine:
Math Department
But then I chec
Paul Harper writes:
> he other thing is in the end I have to convert from the .tex file to a
> .docx file using pandoc
Org exports to odt via ox-odt. You can presumably export directly to docx
using org-odt-convert-processes.
—Rasmus
--
Together we will make the possible totay impossible
Hi Titus,
Titus von der Malsburg writes:
> Parentheses are punctuation, so the $ in my example should be
> interpreted as math delimiters. I think whoever wrote the code, simply
> overlooked parentheses when implementing the punctuation part.
I believe the problem is complicated.
In principal
Hi
more info and a reproducible example:
when exporting the following org file
--8<---cut here---start->8---
* A link to a non existent file
[[file:~/NONEXISTENT.org::*SOMETHING][Link to header in non existing org file]]
--8<---cut here---
26 matches
Mail list logo
