Emacs : GNU Emacs 23.4.1 (i686-pc-cygwin, GTK+ Version 2.24.8)
of 2012-01-29 on fiona
Package: Org-mode version 7.8.09
This bug concerns org-tables.
Field formulas with hline-address on right-hand side don't work anymore.
See the formula below the next table.
There, the address on the
It is not really an Org Mode solution but, if HTML is an acceptable
output format, I would imagine that you can concoct some CSS to make the
HTML look the way you want it to.
You can add CSS via the `style' keyword. It can go in projects (see Info
section 13.3.1,2) or in the file itself (see 1
Charles wrote:
> I'm fairly new to Org and did an experiment. Perhaps only one #+TBLFM: per
> table is allowed since the plural is used
.
.
.
Thanks, Charlie. I think you must be correct. Since posting my message, I've
run across the notion of using " C-c ' " within a table to edit formulas.
Mike,
I'm fairly new to Org and did an experiment. Perhaps only one #+TBLFM:
per table is allowed since the plural is used
15.6 Summary of in-buffer settings
==
. . .
`#+TBLFM:'
This line contains the formulas for the table directly above the
line.
I need control over the font used for results of inline computations in
exported files.
When I have the following code
This is inline R 1+2 = src_R{1+2}
and export it to html (or LaTeX) the fonts used for the regular text and the
fonts used for the results
of the computation are different. Is
John Hendy writes:
> -- On that note, what's the best way to get data out of
> org-habit/headlines and into something a bit more usable like csv? I'm
> looking for something more than just looking through headlines for
> missed days. I'm going to need full access to the time stamps in a
> usable
Greetings. I'm having difficulty applying multiple formula expressions to an
Org-mode table. For example, if I start with:
#+TBLNAME: test
| 1 | 2 | |
| 4 | 5 | |
| 7 | 8 | 9 |
#+TBLFM: @1$3='(+ 10 7)
#+TBLFM: @2$3='(+ 11 9)
and then position the cursor on the f
Simon Thum writes:
> I'm sure there is a better way to fix this, but the attached patch
> helps me to not get something like "Warning: argument nil not
> recognized" spoiling every maxima result.
I'd rather do this directly in the let form:
-(let* ((cmdline (cdr (assoc :cmdline params)))
Hello,
Steinar Bang writes:
>> Steinar Bang :
>
>> I use M-up and M-down a lot to move items in plain lists up and down in
>> the list. In the org-mode delivered with emacs 23 the item you moved
>> past stayed folded. But in git org-mode and in 7.8.09, the item you
>> move past is opened.
> Steinar Bang :
> I use M-up and M-down a lot to move items in plain lists up and down in
> the list. In the org-mode delivered with emacs 23 the item you moved
> past stayed folded. But in git org-mode and in 7.8.09, the item you
> move past is opened.
> Is there a way to get the old beha
Hi all,
I'm sure there is a better way to fix this, but the attached patch helps
me to not get something like "Warning: argument nil not recognized"
spoiling every maxima result.
I guess I might also fix this by adding explicit :cmdline amendments,
but was too lazy to double-check.
Cheers,
Nicolas Goaziou writes:
> This is correct. I was just pointing out (though, admittedly, not very
> clearly) that the final part of the next sentence in the manual,
> "sometimes it is convenient to put them into a comment line", isn't.
It might be worth making the manual clear, so users know what
Hi Nicolas,
>> I'm trying to define a new emphasis
>
> Please don't. We're in the process of hard-coding emphasis markers.
OK. Understood.
>> that would work like org-code (=) except that it would export to
>> \textsf instead of \texttt in LaTeX.
>
> If that's related to export, you can twea
Hello,
"Francesco Pizzolante" writes:
> My goal is, in fact, to keep the default behavior of the '=' marker and
> redefine
> the behavior of the '~' marker.
>
> I'd like '~' to behave exactly the same way = does but using \textsf instead
> of
> \texttt. Is it possible?
Certainly. Even if we
Emacs : GNU Emacs 23.4.1 (i686-pc-cygwin, GTK+ Version 2.24.8)
of 2012-01-29 on fiona
Package: Org-mode version 7.8.09
This bug concerns org-tables.
Field formulas with hline-address on right-hand side don't work anymore.
See the formula below the next table.
There, the address on t
Hello,
"Francesco Pizzolante"
writes:
> I'm trying to define a new emphasis
Please don't. We're in the process of hard-coding emphasis markers.
> that would work like org-code (=) except that it would export to
> \textsf instead of \texttt in LaTeX.
If that's related to export, you can twe
Colin Hall writes:
> Tim Burt rochester.rr.com> writes:
>>
>> I want to gather data from properties into something that can be used by
>> a babel source block (e.g. plot the data). Searches in the manual,
>> worg, and gmane have not yielded the method, but my best guess is that
>> I've missed i
Tim Burt rochester.rr.com> writes:
>
> I want to gather data from properties into something that can be used by
> a babel source block (e.g. plot the data). Searches in the manual,
> worg, and gmane have not yielded the method, but my best guess is that
> I've missed it. If so, this is simply a
Hello,
I have the same problem and resolved it with the appended
patch. Apparently, the .out-files aren't created and therefore can't be
deleted. The patch is checking for file-existence before trying to
delete.
Greetings, Benjamin
diff --git a/lisp/org.el b/lisp/org.el
index 16d2fe0..40fc646 10
Andreas Leha writes:
> I am trying to use % in a caption on the new exporter. Both, % and \%,
> fail. What is the proposed method?
>
> Test case:
>
> #+caption: The values in \%
> | 1 | 3 |
> | 2 | 1 |
This should be fixed now. No need to protect the percent sign.
Thanks again for your report
Hi Nicolas,
>> when exporting this with the new exporter, the line #+name: plot_baz is
>> exported literally to the both, LaTeX and ODT. Is this a bug?
>>
>> #+name: plot_baz
>> #+begin_src R :exports results :results graphics :file fig_baz.png
>> plot(1:10) #+end_src
>>
>> #+caption: BAZ
>> #+
Andreas Leha writes:
> I had to add (italic . "Italic") to the definition of
> org-e-odt-default-org-styles-alist in contrib/lisp/org-e-odt.el to get
> /italic/ text exported correctly to odt.
I recently have split `emphasis' object type into `bold', `italic',
`underline' and `strike-through' an
Andreas Leha writes:
> when exporting this with the new exporter, the line #+name: plot_baz is
> exported literally to the both, LaTeX and ODT. Is this a bug?
>
> #+name: plot_baz
> #+begin_src R :exports results :results graphics :file fig_baz.png
> plot(1:10) #+end_src
>
> #+caption: BAZ
> #
Richard, this is great! Thank you.
--Chris
Richard Lawrence wrote:
Richard Lawrence writes:
Try this: in your .emacs, add the following code:
(defun prompt-for-lastname-and-upcase ()
(upcase (read-string "Last name: ")))
This defines a function that will prompt the user to type a last
Hi all,
I am trying to use % in a caption on the new exporter. Both, % and \%,
fail. What is the proposed method?
Test case:
#+caption: The values in \%
| 1 | 3 |
| 2 | 1 |
Regards,
Andreas
Hi all,
I had to add (italic . "Italic") to the definition of
org-e-odt-default-org-styles-alist in contrib/lisp/org-e-odt.el to get
/italic/ text exported correctly to odt.
Is that a known/intended limitation?
Regards,
Andreas
Hi all,
when exporting this with the new exporter, the line #+name: plot_baz is
exported literally to the both, LaTeX and ODT. Is this a bug?
#+name: plot_baz
#+begin_src R :exports results :results graphics :file fig_baz.png
plot(1:10)
#+end_src
#+caption: BAZ
#+label: fig-baz
#+results: plo
Hi Nicolas,
>> The LaTeX file looks like this:
>> ,
>> | [...]|
>> | \begin{document} |
>> | |
>> | \maketitle
Hello,
Andreas Leha writes:
> The LaTeX file looks like this:
> ,
> | [...]|
> | \begin{document} |
> | |
> | \maketitle
Hi Nicolas,
thanks once more for the prompt reaction!
>
>> #+TITLE: Test subscripts
>> #+OPTIONS: ^:{}
>>
>> * Test
>> Hi all,
>>
>> there seems to be a problem with the option above in the new
>> exporter, as this_o is exported as subscript for me.
>
> I tried various values for `org-export-with-
Hello,
Andreas Leha writes:
> #+TITLE: Test subscripts
> #+OPTIONS: ^:{}
>
> * Test
> Hi all,
>
> there seems to be a problem with the option above in the new
> exporter, as this_o is exported as subscript for me.
I tried various values for `org-export-with-sub-superscripts' and
`org-use-sub-su
#+TITLE: Test subscripts
#+OPTIONS: ^:{}
* Test
Hi all,
there seems to be a problem with the option above in the new
exporter, as this_o is exported as subscript for me.
Cheers,
Andreas
I use M-up and M-down a lot to move items in plain lists up and down in
the list. In the org-mode delivered with emacs 23 the item you moved
past stayed folded. But in git org-mode and in 7.8.09, the item you
move past is opened.
Is there a way to get the old behaviour back? Ie. that items you
Hi,
I'm trying to define a new emphasis that would work like org-code (=) except
that it would export to \textsf instead of \texttt in LaTeX.
I tried several combinations using org-emphasis-alist and
org-export-latex-emphasis-alist, but I must admit that I'm lost amongst all
parameters controllin
Nicolas Goaziou writes:
[...]
> On the other hand, every regular target will be invisible. Let me
> explain.
>
> At the moment, "<>" and "# <>" produce, respectively, " name="tag" id="tag">tag" and "".
>
> In a not so distant future "<>" will produce " id="tag">" and "# <>" will be ignored.
And
Hello,
François Pinard writes:
> When some feature is being deprecated, the Org manual should tell us,
> then ! :-) And at least where that feature is documented. Currently,
> the manual says:
>
> The preferred match for a text link is a dedicated target: the same
> string in double angular
36 matches
Mail list logo
