Hello,
In the following example (latest Org), with point at "|", when TAB is
pressed, block gets hidden at the "name" level.
--8<---cut here---start->8---
|#+name: test
#+begin_src emacs-lisp
"test"
#+end_src
--8<---cut here---end---
Hi
It used to be the case that you could assign a variable and any
whitespace would be chomped:
--8<---cut here---start->8---
#+begin_src emacs-lisp :var a = 1 :var b = 2
(+ a b)
#+end_src
--8<---cut here---end--->8---
H
Martyn Jago writes:
(Fixed typos in heading)
Hi
It used to be the case that you could assign a variable and any
whitespace would be chomped:
#+begin_src emacs-lisp :var a = 1 :var b = 2
(+ a b)
#+end_src
However it is now required to remove the whitespace:
#+begin_src emacs-lisp :var a=
Hi everybody,
I've been using org-mode for quite a while but only recently found
myself in need of using ditaa to draw some simple diagram. As it turns
out my installation of emacs(Ubuntu 10.10, emacs-snapshot from
https://launchpad.net/~cassou/+archive/emacs) doesn't come with
ditta.jar pre-bund
TP writes:
> Apparently the S1500's are supported on Linux via Sane
> (http://www.sane-project.org/sane-backends.html#S-FUJITSU). Don't see
> any mention of the S1300 (but it probably also works?).
I can confirm that the S1300 works well with Linux.
Best,
Matt
On Sun, 13 Nov 2011 12:57:21 -0500, Nick Dokos wrote:
> > 1) If I don't pass -c to emacsclient, then I need to search all my
> >workspaces to find where emacs decided to put the capture frame
> > 2) If I pass do pass -c to emacsclient, then I need to close the frame
> >afterwards. And more
Hi Martyn,
Tom mentioned this regression earlier and I treated it as a new
restriction on variable specifications, but if multiple people are
running into this issue I suppose spaces around equals should be
supported.
I have just pushed up a change and a test case ensuring that examples
like your
Hi Andrey,
The variable `org-ditaa-jar-path' can be used to specify a non-standard
location for the ditaa jar file. Org-mode has *many* customization
variables, and for most problems a variable will exist to solve the
problem, the `apropos' command can be very useful for finding these
variables.
Nicolas Goaziou writes:
> Hello,
>
> In the following example (latest Org), with point at "|", when TAB is
> pressed, block gets hidden at the "name" level.
>
> |#+name: test
> #+begin_src emacs-lisp
> "test"
> #+end_src
>
> It is because `org-babel-result-regexp' is matched in
> `org-babel-hide-
Eric Schulte writes:
> "name" is and should be an element of the `org-babel-data-names' list as
> it is the preferred way to name data in an Org-mode file, e.g.,
>
> #+name: foo
> - 1
> - 2
> - 3
I agree.
> The only reason that "tblname" and "results" are included in the list
> are because "tbl
Eric Schulte writes:
> Hi Andrey,
>
> The variable `org-ditaa-jar-path' can be used to specify a non-standard
> location for the ditaa jar file.
True, but my patch is not about doing away with `org-ditaa-jar-path'
variable, it is about broadening the definition of "standard location"
so to speak
It takes long to export the whole file when it contains many babel
stuff. And in many cases, I just want to check if the current frame is
arranged as expected. SO I just want to know if there is some convenient
way to export just one frame without tagging all the other frames as :noexport.
12 matches
Mail list logo