Hi Nicolas,
Nicolas Goaziou writes:
> ((adaptive-fill-function (quote nil)) (adaptive-fill-regexp (quote \(\([
[...]
This looks good.
> It's the same as the previous bug: when I try to debug
> `org-indent-line-function', the problem disappears.
I pushed another fix: I now rely on the existin
Hi Matt,
Matt Lundin writes:
> * lisp/org-footnote.el (org-footnote-new): Don't call
> org-footnote-unique-label if org-footnote-auto-label is set to
> random.
>
> Calling org-footnote-unique-label calls org-footnote-all-labels, which
> can dramatically slow down footnote creation in a buffe
Hello,
Yesterday I've updated my git clone of org-mode after a few weeks of
not found time to. I noticed the latex fragment preview (C-c C-x C-l)
broke. I get messages like
org-create-formula-image-with-dvipng: Removing old name: No such
file or directory, /tmp/orgtex17198KSG.out
Interesti
Hi list.
I try to process my data in python. I store outputs from different
scripts in separate txt files and load data using numpy.loadtxt. I want
to change it store outputs in results tables.
So I have this example table
#+TBLNAME: test-table
| 1e212 | 2e1 | 23e3 |
and use it as variable
hey,
First I just wanted to thank everyone involved in creating orgmode,
it's amazing and it has pretty much sold me on emacs. But, I've had
some problems with links containing æøå. I'm an osx (lion) user. In
emacs 23.4 (9.0) no paths with æøå where possible to open. For
example, these did not wor
Hi all,
there seems to be a bug in babel in connection with interactive
source block evaluation when the header argument :eval no-export
(ditto with never-export) is present.
I get "Evaluation Disabled" when I try to evaluate (C-c C-c) this block:
#+begin_src R :session *R* :exports none :eval n
Nicolas,
unfortunately, I have immediately run into another problem with the new
exporter (to latex) when going back to my long document (a project
proposal).
I have a minimal example which illustrates the problem. The attached
are a simple org file with the resulting latex file. The key proble
Bastien writes:
> Hi Nicolas,
>
> Nicolas Goaziou writes:
>
>> ((adaptive-fill-function (quote nil)) (adaptive-fill-regexp (quote \(\([
>
> [...]
>
> This looks good.
>
>> It's the same as the previous bug: when I try to debug
>> `org-indent-line-function', the problem disappears.
>
> I pushed a
Eric Fraga writes:
> unfortunately, I still have problems. I am using org completely up to
> date (a few minutes ago).
me too, I just posted on the gnus.user list ...
--
cheers,
Thorsten
Hi Andreas,
This works for me, could you try to reproduce the problem with emacs -Q,
to check if maybe the cause lies in your personalization?
Best,
Andreas Leha writes:
> Hi all,
>
> there seems to be a bug in babel in connection with interactive
> source block evaluation when the header argu
Hi Eric,
Eric Fraga writes:
> unfortunately, I still have problems. I am using org completely up to
> date (a few minutes ago). I do not turn orgstruct++-mode on
> automatically at all any more but instead turn it on manually by
>
> M-x orgstruct++-mode RET
>
> once I'm in a Message buffer.
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I can't get a \begin{figure*} environment with multicolumn.
>>
>> Org-mode
>> #+CAPTION: A sample black and white graphic (.eps format) that needs to span
>> two columns of text.
>> #+ATTR_LaTeX: multicolu
Hello,
Eric Fraga writes:
> unfortunately, I have immediately run into another problem with the new
> exporter (to latex) when going back to my long document (a project
> proposal).
> I have a minimal example which illustrates the problem. The attached
> are a simple org file with the resulti
t...@tsdye.com (Thomas S. Dye) writes:
> The new exporter does a nice job with the ACM-SIG template at
> http://github.com/tsdye/orgmode-ACM-template.
Nice.
I will merge some changes to the export engine during the next week,
then I'll try to send to the ML a little summary on the various ways
Hi Eric,
thanks for the quick response on a bogus bug. I can not reproduce it
myself now. Seems it was the result from being in the middle of an
update.
Sorry for the noise,
Andreas
* Hi all,
for me the new latex exporter seems to ignore the :noexport: tag with
regard to source block execution.
If I export this example, both source blocks get evaluated.
(It works well, if I limit the scope of the export to a subtree)
** Do NOT export this
Hello,
Andreas Leha writes:
> for me the new latex exporter seems to ignore the :noexport: tag with
> regard to source block execution.
>
> If I export this example, both source blocks get evaluated.
:noexport: isn't a directive that Babel recognizes. As a consequence,
a :noexport: tag won't p
Hi, Org people.
I'm not sure I'm using "# <>" correctly, but my feeling is that it
should stick to the following text in various Org operations. Let's say
I have something like (as I think it):
--8<---cut here---start->8---
* Some container
# <>
* Title 1
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> for me the new latex exporter seems to ignore the :noexport: tag with
>> regard to source block execution.
>>
>> If I export this example, both source blocks get evaluated.
>
> :noexport: isn't a directive that Babel re
Hello,
François Pinard writes:
> I'm not sure I'm using "# <>" correctly, but my feeling is that it
> should stick to the following text in various Org operations. Let's say
> I have something like (as I think it):
"# <>" is a deprecated construct. I suggest to avoid bothering with
it.
Regar
Nicolas Goaziou writes:
> Hello,
>
> Eric Fraga writes:
>
>
>> unfortunately, I have immediately run into another problem with the new
>> exporter (to latex) when going back to my long document (a project
>> proposal).
>
>> I have a minimal example which illustrates the problem. The attached
>>
I work for a public health department. Twice in the past 5 years we have
had to open evacuation shelters during a flood, for anywhere from 80 to
120 medically-frail evacuees. Our documentation system (paper) has
improved, but it is still not ideal. I am experimenting with whether
org-mode could
Nicolas Goaziou writes:
> "# <>" is a deprecated construct.
Sigh! I just spent a few hours adding many of those and making sure
everything is regular.
When some feature is being deprecated, the Org manual should tell us,
then ! :-) And at least where that feature is documented. Currently,
the
Nicolas Goaziou wrote:
> Hello,
>
> François Pinard writes:
>
> > I'm not sure I'm using "# <>" correctly, but my feeling is that it
> > should stick to the following text in various Org operations. Let's say
> > I have something like (as I think it):
>
> "# <>" is a deprecated construct. I
François Pinard writes:
> Nicolas Goaziou writes:
>> I suggest to avoid bothering with it.
> I hope the letter I wrote at the beginning of this little thread is
> not going to be dismissed or ignored.
Well, my original message accidentally left my machine before it was
finished. I completed i
Hi Chris,
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 name
into the minibuffer, converts the result into uppercase, and returns it
as a string.
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 name
> into the minibuffer, converts the result into uppercase,
Bastien writes:
> Hi Eric,
Hello Bastien!
[...]
> You are using the exact same version of Gnus and Emacs than I do.
> Unless you forgot to reload the correct (uncompiled?) version of
> Org -- I barely dare suggesting this :) -- then this comes from
> something in your configuration.
Definite
John Hendy writes:
[...]
> @EricFraga: if implementing the LaTeX gantt package has moved into
> either of the two actionable categories you mentioned in our last
> discussion
> (http://lists.gnu.org/archive/html/emacs-orgmode/2011-08/msg01259.html),
> I'd be happy to hear about it :)
Unfortuna
Herbert Sitz writes:
> I was playing around with Evil and like it quite a bit. It feels better than
> the previous Viper/Vimpulse package I was using, plus documentation is good,
> clear, and it seems easy to customize.
>
> One problem with Org for me has been keybindings. Even with a Vim emula
Nick Dokos writes:
> Nicolas Goaziou wrote:
>
>> Hello,
>>
>> François Pinard writes:
>>
>> > I'm not sure I'm using "# <>" correctly, but my feeling is that it
>> > should stick to the following text in various Org operations. Let's say
>> > I have something like (as I think it):
>>
>> "#
l use that construct extensively and look forward to the clarification.
Yours,
Christian
---
Sent from mobile.
Please excuse my brevity.
Hi Folks,
Is there a function to extract the body of an item minus all the
auxiliary information?
* Item
This is the text I want.
And here is the second line.
SCHEDULED: <2012-05-12>
DEADLINE: <2012-05-13>
:PROPERTIES:
:foo: bar
:END:
And it's conceivable there is more below dr
33 matches
Mail list logo
