Nicolas Goaziou nicolasgoaziou.fr> writes:
>
> Amitai Hoze gmail.com> writes:
>
> > Hi, sorry, I opened the page and the mistake is still there.
>
> The page may take some time to be updated. However, the texi manual is
> fixed.
>
> Regards,
>
>
I came upon this mistake too.
http://orgmo
On Tue, Dec 30, 2014 at 1:49 PM, Alexandre Norman wrote:
>
> Hello,
>
> I just wrote two python scripts to transform a project managed in
> org-mode in (beautifull) gantt graphes.
>
> You could find more here :
> - example of generated graphes :
> - http://xael.org/norman/pyt
Ken Mankoff writes:
> OK. If I set that to nil then the links are not at the bottom of the
> section, they are inline. But ASCII (in my opinion) shouldn't have
> links.
I disagree. It is a bug to silently ignore every link in ASCII export.
> Can you advise how I get no links (or is it no notes?
Felix Fernandes writes:
>> You probably need to make sure that you install org correctly, so that
>> the previous bits are shadowed completely. Read the "Using Emacs
>> packaging system" subsection of the "Installation" section of the Org
>> manual for important information:
>>
>>(info "(org
* On 2015-01-01 at 13:59, Ken Mankoff wrote:
> OK. If I set that to nil then the links are not at the bottom of the
> section, they are inline. But ASCII (in my opinion) shouldn't have
> links. If I wanted links, I'd use Org or Markdown. Can you advise how
> I get no links (or is it no notes?) at
* On 2015-01-01 at 13:36, Nicolas Goaziou wrote:
>> When I export to ASCII, things look mostly great. Except, at the
>> bottom of every section, I have the "raw" Org citations repeated.
>> That is, if I [[cite:Foo2001]] somewhere in the text, at the bottom
>> I'll see:
>>
>> [(Foo, 2001)] cite:Fo
Hello,
Ken Mankoff writes:
> I have the following setup for citing in Org documents:
>
> (org-add-link-type
> "textcite" (lambda (key) (org-open-file cby-references-file t nil key))
> (lambda (path desc format)
>(cond
> ((eq format 'latex) (format "\\textcite{%s}" path))
> ((eq fo
Hello,
42 147 writes:
> I'm looking for a way to copy only the headlines and sub-headlines, etc., in
> org-mode, without any of the text that had been folded into them.
> Thus:
See `org-copy-visible'.
Regards,
--
Nicolas Goaziou
I'm looking for a way to copy only the headlines and sub-headlines, etc., in
org-mode, without any of the text that had been folded into them. Thus:
/* Bach.
[commentary]
/** Well-Tempered Clavier.
[commentary]
/*** Book I.
[commentary]
/ Prelude in C Major.
[commentary]
Would become:
Am 30.12.2014 um 06:02 schrieb Calvin Young :
> Hey all,
>
> Does anyone know whether the version of OSX Emacs from
> http://emacsformacosx.com/ comes with all of the org-mode contrib packages?
Yes:
;; This file is not part of GNU Emacs.
> If so, I'm having a heck of a time finding it.
These
Hi Karl
On Thu, Jan 1, 2015 at 5:27 PM, Karl Voit wrote:
> Is there a similar method to re-direct the stderr of a shell script
> to stdout as well?
Not that I know of an other way than what you already demonstrated.
Once I wrote a lengthy post with my opinion about stdout, stderr and
the exit s
Hi,
I have the following setup for citing in Org documents:
(org-add-link-type
"textcite" (lambda (key) (org-open-file cby-references-file t nil key))
(lambda (path desc format)
(cond
((eq format 'latex) (format "\\textcite{%s}" path))
((eq format 'ascii) (format "@%s" path))
))
Hi!
I enjoyed [1] where John is describing the issue of vanishing
stderr-messages through babel.
This could be fixed by "(setq org-babel-python-command "python -i -c
\"import sys; sys.stderr = sys.stdout\"")".
Is there a similar method to re-direct the stderr of a shell script
to stdout as well?
* Marcin Borkowski wrote:
>
> On 2014-12-31, at 14:49, Ista Zahn wrote:
>
>> Yes, google is very convenient.
>
> That's why they're so dangerous.
In case you're survey data contains privacy-related sensible data,
you can not use Google anyhow - I do think that there's no need to
mention this exp
14 matches
Mail list logo
