Eric Schulte writes:
In defense of the existing behavior, I don't see the benefit of calling
a code block with the same arguments from multiple locations and
subsequently littering a file with multiple identical results blocks.
I agree that this didn't make all that much sense in the past, but
Hello!
With the input-method TeX it is easy to insert more graphical Unicode
characters such as • (\bullet). Some questions about that:
1. Is it possible to make org-mode use • as a bullet character for lists?
2. Is it possible to make another persons org-mode installation aware of
this when
Hi Eric
On Wed, Jun 26, 2013 at 12:41 AM, Eric Schulte schulte.e...@gmail.com wrote:
I think we could be well served by discussing how people use call lines,
how they would use call lines (if this behavior changed), and what
behavior would best support these existing and potential use cases.
Hello,
Georg Lehner jorge-...@magma.com.ni writes:
In LaTeX export I have the following behaviour:
[[*Headline][Headline]] converts to a Hyperlink to the respective
headline with description text 'Headline'.
[[*Headline]] converts to the respective headline number
In ODT export both
Nicolas Richard theonewiththeevill...@yahoo.fr writes:
I just noticed this thread, which i think reports exactly the issue I
reported here [this thread was before, but the title didn't catch my
eyes -- sorry about that] 87zjuv2r79@yahoo.fr and more or less
fixed here
Hi,
With the input-method TeX it is easy to insert more graphical Unicode
characters such as • (\bullet). Some questions about that:
1. Is it possible to make org-mode use • as a bullet character for lists?
2. Is it possible to make another persons org-mode installation aware of
this when
Hi Vikas,
Vikas Rawal wrote:
I am trying to use textpos to position images at specific location on
a frame.
I now use TikZ to do that. I have the impression it is easier. Though, I have
the real impression of writing LaTeX inside an Org buffer... which I dislike.
I'd like to write text as
Hello,
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org
writes:
Vikas Rawal wrote:
For example, if I use the following:
(add-to-list 'org-beamer-environments-extra
'(textpos1 w \\begin{textblock}%h \\visible %a { }
\\end{textblock}))
and write the
On 2013-06-26 02:29, Achim Gratz wrote:
Eric Schulte writes:
In defense of the existing behavior, I don't see the benefit of calling
a code block with the same arguments from multiple locations and
subsequently littering a file with multiple identical results blocks.
I agree that this didn't
My vote is for adding #+name support to call lines, and then handling
their results in the same manner as code block results.
Achim Gratz strom...@nexgo.de writes:
I'm not sure what this would entail other than replacing the call with
its arguments with the name of the call in the results
Michael Brand michael.ch.br...@gmail.com writes:
Hi Eric
On Wed, Jun 26, 2013 at 12:41 AM, Eric Schulte schulte.e...@gmail.com wrote:
I think we could be well served by discussing how people use call lines,
how they would use call lines (if this behavior changed), and what
behavior would
Hello,
Rick Frankel r...@rickster.com writes:
At the time (late 2012) I found Nicolases changes (named results
blocks, attributes and captions on the results block and not the
source, etc) confusing. I still find it odd that you need to evaluate
a source block before you can e.g, add a
Hi!
I was looking for a reasonable simple method to define processes and
work-flows within Org-mode. My research did not result in anything
existing I found useful. Therefore, I started to read about dot[1]
and found [2].
I would like to define my diagram with the following two tables: one
for
Nicolas-
On 2013-06-26 11:13, Nicolas Goaziou wrote:
Rick Frankel r...@rickster.com writes:
At the time (late 2012) I found Nicolases changes (named results
blocks, attributes and captions on the results block and not the
source, etc) confusing. I still find it odd that you need to evaluate
a
Sorry, minor mistake: I could not find out why dot is not able to
mix directed and not directed graphs in one diagram. Therefore I had
to replace th - in the node table with and the corresponding
results as well:
#+name: foobar-node-table
| *node* | *label*| *shape* |
On 2013-06-26 11:23, Karl Voit wrote:
Hi!
I would like to define my diagram with the following two tables: one
for the node definitions and one for the interconnections between
notes. The syntax should be pretty self-explanatory (or at least I
hope so):
I (not an ELISP hacker) would have to use
Rick Frankel r...@rickster.com writes:
Nicolas-
On 2013-06-26 11:13, Nicolas Goaziou wrote:
Rick Frankel r...@rickster.com writes:
At the time (late 2012) I found Nicolases changes (named results
blocks, attributes and captions on the results block and not the
source, etc) confusing. I
Karl Voit devn...@karl-voit.at writes:
Hi,
I was looking for a reasonable simple method to define processes and
work-flows within Org-mode. My research did not result in anything
existing I found useful. Therefore, I started to read about dot[1]
and found [2].
[...]
Some (still missing)
Hi Eric
On Wed, Jun 26, 2013 at 4:54 PM, Eric Schulte schulte.e...@gmail.com wrote:
http://thread.gmane.org/gmane.emacs.orgmode/72513/focus=73547
They will overwrite eachother's results.
I do not understand. In order to avoid that they will overwrite
eachother's results I added
* Rick Frankel r...@rickster.com wrote:
Two things:
1. You don't need to write table parsing code, as passing in a
table as an argument to a code block will convert it to an
array.
#+name: ptable
| head1 | head2 |
|---+---|
| a | 1 |
| b
I am sorry, I wanted to say that I want to do something like
(note: not current behavior)
---
#+NAME: i_am_curious_how_this_works
#+BEGIN_SRC emacs-lisp
(format %s org-babel-current-src-block-location)
#+END_SRC
#+CALL:
Hi Karl,
Karl Voit devn...@karl-voit.at writes:
I was looking for a reasonable simple method to define processes and
work-flows within Org-mode. My research did not result in anything
existing I found useful. Therefore, I started to read about dot[1]
and found [2].
I would like to define my
On 2013-06-26 13:03, Karl Voit wrote:
* Rick Frankel r...@rickster.com wrote:
Two things:
1. You don't need to write table parsing code, as passing in a
table as an argument to a code block will convert it to an
array.
t=[[a, 1], [b, 2]]
You're
Hi,
I am using the *old* exporter (the packaged version in Debian Wheezy),
I don't know if this behaviour keeps happening with the new one. I
have come up with a minimal case that exhibits this problem — Might be
my fault for using this feature wrongly, but it *feels* as a parser
error.
The
Hi François
Your post with the first-hand background about Lilypond is a very
interesting read for me, thank you.
On Wed, Jun 26, 2013 at 5:13 AM, François Pinard
pin...@iro.umontreal.ca wrote:
but really, this is of no interest nowadays.
In my opinion, Lilypond is immensely more appealing!
I've finally found the cause of a long lasting problem between Org and the dev
version of Emacs 24.4. Though, I don't understand it... Anyone?
When opening Org from my Emacs 24.3.1, everything's OK.
Same .emacs file, same everything, but latest version of Emacs: bang!
--8---cut
Debugger entered--Lisp error: (wrong-type-argument symbolp (autoload
[...]
interactive-form((autoload org-agenda Activate appointments found
[...]
advice--make-interactive-form(ad-Advice-org-agenda-to-appt (autoload
I installed a patch into trunk that should fix this, thank you.
On 06/25/2013 03:35 AM, Vikas Rawal wrote:
At the end of the export process I get the message:
content.xml changed on disk; really edit the buffer? (y, n, r or C-h)
Please type y, n or r; or ? for help
After typing 'y', I have to reconfirm with 'yes' and then with 'y' again to
get a valid
Hello,
I wonder how to use 'org-file-apps'.
As I understand, when I run ~C-c C-o~ on a link of form
[[file:file.pdf][a PDF file]] Org mode uses this variable to decide how
to 'open' this type of file. Instead of docview mode of Emacs I want to
use Okular (it allows to select text from PDF file),
Eric Schulte writes:
My vote is for adding #+name support to call lines, and then handling
their results in the same manner as code block results.
Achim Gratz strom...@nexgo.de writes:
I'm not sure what this would entail other than replacing the call with
its arguments with the name of the
Vladimir Lomov lomov...@gmail.com writes:
#+BEGIN_SRC emacs-lisp :tangle org-apps-c.el
(add-to-list 'load-path /usr/share/emacs/site-lisp/org)
(require 'org)
(setq org-file-apps
'( (\\.pdf::\\(\\d+\\)\\' . run-me --page %1 %s)
(\\.pdf\\' . run-me %s)
)
)
#+END_SRC
31 matches
Mail list logo
