Hello,
Bastien b...@gnu.org writes:
Beside, `org-flag-drawer' is currently under revision since Michael
report on slowliness (and recent discussion with Tod and Aaron.)
I rewrote `org-flag-drawer' a few days ago. It shouldn't be slow if
cache is activated.
Regards,
--
Nicolas Goaziou
Hello Aaron and Bastien,
Aaron Ecay wrote:
The property drawer after the code block is a red herring: the following
file (with no real property drawer at all) misbehaves on property
setting and getting functions, with the fake properties in the code
block behaving as though they pertained to
Hello Eric,
Eric Schulte wrote:
Sebastien Vauban sva-n...@mygooglest.com writes:
Here is a small patch to improve the messages displayed by Org Babel when
processing code blocks: now, you get the line number added to the output, so
that you can easily find afterward which block had problems,
Bastien b...@gnu.org writes:
Hi Aaron and Tod,
Aaron Ecay aarone...@gmail.com writes:
This seems like an excellent use case for the parser: basically a bunch
of uses of org-*-regexp and org-re-property need to be augmented with
a check like:
(not (memq (org-element-type
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@gnu.org writes:
Beside, `org-flag-drawer' is currently under revision since Michael
report on slowliness (and recent discussion with Tod and Aaron.)
I rewrote `org-flag-drawer' a few days ago. It shouldn't be slow if
Nicolas Goaziou n.goaz...@gmail.com writes:
I'm slowly working on introducing these functions in basic parts of Org
(e.g. fontification, indentation). Then I will target other functions
not using them yet. There's a lot to do. Help is welcome. IMO, at the
bare minimum, new or rewritten
Hi Mark,
the patch is unreadable -- can you resend it as an attachment?
Thanks!
--
Bastien
Hi Thomas,
t...@tsdye.com (Thomas S. Dye) writes:
With the following Org mode file, there is a dead space where
org-insert-heading doesn't do anything. In the following example, if the
point is on either of the empty lines marked [dead space] no heading is
created.
Is this behavior
Hi François,
François Pinard pin...@iro.umontreal.ca writes:
Not a big problem, and I expect that someone on this list will reply
that this is an Org limitation (a way to say that the bug is innocuous
enough to not deserve a correction). I rather use the word limitation
for a bug which has
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
This patch fixes the error, but it looks strange (indentation is still
unchanged for clarity). Not sure if this an Ert or Emacs error, though.
I suggest you handle this the way you prefer: either by committing
this in Org before asking
Hello,
how does org-mode 'decide' whether a linked filed (C-c C-l) should be
opened (C-c C-o) inside an Emacs buffer or opened by an external program? I
am using Emacs 24.3 for Windows and org-mode 8.2
PDF files are opened in Acrobat, but JPGs are opened in a buffer (but are
not properly
Hi all,
how do I reference the results of a #+call line?
Here are my unsuccessful attempts:
--8---cut here---start-8---
* Test call results
#+name: curdir
#+begin_src sh
echo $PWD
#+end_src
#+results: curdir
: /home/andreas/tmp/junk/2013/11
#+name:
Hi, Christof,
Il Mercoledì 13 Novembre 2013 11:19, Christof Spitz christof.sp...@gmail.com
ha scritto:
how does org-mode 'decide' whether a linked filed (C-c C-l) should be opened
(C-c C-o) inside an Emacs buffer or opened by an external
program? I am using Emacs 24.3 for Windows and
Andreas Leha wrote:
how do I reference the results of a #+call line?
Here are my unsuccessful attempts:
* Test call results
#+name: curdir
#+begin_src sh
echo $PWD
#+end_src
#+results: curdir
: /home/andreas/tmp/junk/2013/11
#+name: curdircall
#+call: curdir()
#+results:
Andreas Leha wrote:
how do I reference the results of a #+call line?
Here are my unsuccessful attempts:
* Test call results
#+name: curdir
#+begin_src sh
echo $PWD
#+end_src
#+results: curdir
: /home/andreas/tmp/junk/2013/11
[...]
#+begin_src sh :var test=curdircall()
echo
Bastien b...@gnu.org writes:
Is the cache activated by default?
Yes, it is.
There's an emergency variable, `org-element-use-cache' to disable it,
but it should be used for debugging purpose only. From the user point of
view, if the cache appears to be corrupted due to a bug, it may be
simpler
Sebastien Vauban sva-n...@mygooglest.com
writes:
Andreas Leha wrote:
how do I reference the results of a #+call line?
Here are my unsuccessful attempts:
* Test call results
#+name: curdir
#+begin_src sh
echo $PWD
#+end_src
#+results: curdir
: /home/andreas/tmp/junk/2013/11
Thanks for the details. I think I've seen the cache corrupted
several times, I didn't know it was this. Any direction on how
to debug such problems? The symptoms were that moving around
with M-down and friends was completely erratic.
--
Bastien
Sebastien Vauban sva-n...@mygooglest.com
writes:
Andreas Leha wrote:
how do I reference the results of a #+call line?
Here are my unsuccessful attempts:
* Test call results
#+name: curdir
#+begin_src sh
echo $PWD
#+end_src
#+results: curdir
: /home/andreas/tmp/junk/2013/11
[...]
Worked!
Great, thanks
Christof
2013/11/13 Giovanni Ridolfi giovanni.rido...@yahoo.it:
Hi, Christof,
Il Mercoledì 13 Novembre 2013 11:19, Christof Spitz
christof.sp...@gmail.com ha scritto:
how does org-mode 'decide' whether a linked filed (C-c C-l) should be
opened (C-c C-o) inside an
Hi Bastien,
Sorry about the formatting -- that's annoying. I've attached the patch.
Here's its description:
Currently there isn't an easy way to have default cell values which
differ from one propview block to another. This patch enables one to
specify what a cell's default value for a
Bastien b...@gnu.org writes:
The attached patch does name indirect buffers after the current tree
heading -- thanks for this idea.
Would anyone else find this useful?
I've now applied this patch, thanks Karl!
--
Bastien
Bastien b...@gnu.org writes:
You can apply the patch you'll find here:
http://article.gmane.org/gmane.emacs.orgmode/78700
Then use C-- 1 C-c C-t to switch to a DONE state even for repeating
events. I'll surely apply the patch on master soon, I'm still waiting
for some feedback.
It's now
Hi Mark,
Mark Edgington edgi...@gmail.com writes:
Currently there isn't an easy way to have default cell values which
differ from one propview block to another. This patch enables one to
specify what a cell's default value for a block should be. For example,
with this patch applied, you
Hi Bastien,
Bastien b...@gnu.org writes:
Hi Thomas,
t...@tsdye.com (Thomas S. Dye) writes:
With the following Org mode file, there is a dead space where
org-insert-heading doesn't do anything. In the following example, if the
point is on either of the empty lines marked [dead space] no
Hi!
I am heavily using time-stamps. With
(setq org-agenda-skip-additional-timestamps-same-entry nil)
I see multiple time-stamps of the same heading on my agenda which I
do like very much for obvious reasons.
However, with a heading such as following I do have a problem:
: ** 2013-12-19
Hello list,
I'm making a presentation in reveal.js with the help of org-mode and
org-reveal and was hoping I could get some help.
I'm trying to remove the table of contents from my slides but the toc
option does not seem to have any effect.
A bare bone presentation on github can be seen in this
Hi Andreas,
Andreas Leha wrote:
Sebastien Vauban sva-n...@mygooglest.com writes:
Andreas Leha wrote:
how do I reference the results of a #+call line?
Here are my unsuccessful attempts:
* Test call results
#+name: curdir
#+begin_src sh
echo $PWD
#+end_src
#+results: curdir
:
Hi Karl,
Karl Voit devn...@karl-voit.at writes:
: ** 2013-12-19 Thu 19:00-23:59 X-Mas-Party
:
: - Email-invitation received: 2013-11-13 Wed
You need to use inactive timestamps in such cases.
From memory, we wanted to preserve the possibility
to have multiple active timestamps in a subtree.
Hi Sebastien,
Sebastien Vauban sva-n...@mygooglest.com
writes:
Hi Andreas,
Andreas Leha wrote:
Sebastien Vauban sva-n...@mygooglest.com writes:
Andreas Leha wrote:
how do I reference the results of a #+call line?
Here are my unsuccessful attempts:
* Test call results
#+name: curdir
* Bastien b...@gnu.org wrote:
Hi Karl,
Hi Bastien!
Karl Voit devn...@karl-voit.at writes:
: ** 2013-12-19 Thu 19:00-23:59 X-Mas-Party
:
: - Email-invitation received: 2013-11-13 Wed
You need to use inactive timestamps in such cases.
This is my work-around so far :-)
From memory, we
* Bastien b...@gnu.org wrote:
Bastien b...@gnu.org writes:
The attached patch does name indirect buffers after the current tree
heading -- thanks for this idea.
Would anyone else find this useful?
I've now applied this patch, thanks Karl!
Thank *you* for implementing this! It helps
Hi Thomas,
t...@tsdye.com (Thomas S. Dye) writes:
I looked more closely and found that the behavior I described happens
when the folded material ends in a list. If I end the list by adding
some regular text, then I get the expected behavior.
Confirmed -- I quickly looked, it seems that
Andreas tjandr...@gmail.com writes:
Hello list,
I'm making a presentation in reveal.js with the help of org-mode and
org-reveal and was hoping I could get some help.
I'm trying to remove the table of contents from my slides but the toc option
does not seem to have any effect.
A bare
Hi Karl,
Karl Voit devn...@karl-voit.at writes:
I am sorry - I do not see the contradiction here.
Sorry, I read too fast.
Why not handle each time-stamp in a consistent manner: show each
-MM-DD ddd as whole-day items on the agenda and -MM-DD
ddd HH:MM as items with an associated
* Bastien b...@gnu.org wrote:
Hi Karl,
Karl Voit devn...@karl-voit.at writes:
I am sorry - I do not see the contradiction here.
Sorry, I read too fast.
:-)
Why not handle each time-stamp in a consistent manner: show each
-MM-DD ddd as whole-day items on the agenda and -MM-DD
Hi Carsten
On Wed, Oct 30, 2013 at 6:59 PM, Michael Brand
michael.ch.br...@gmail.com wrote:
On Fri, Oct 25, 2013 at 3:31 PM, Carsten Dominik
carsten.domi...@gmail.com wrote:
On 24.10.2013, at 22:47, Michael Brand michael.ch.br...@gmail.com wrote:
On Thu, Oct 24, 2013 at 8:18 AM, Carsten
Hi Michael,
Michael Brand michael.ch.br...@gmail.com writes:
The last paragraph has not been answered yet. Can I ask Jason Dunsmore
directly to give me write access to Org?
Please send me your public key and I'll give you write access.
Thanks!
--
Bastien
Hello François,
2013ko azaroak 13an, François Pinard-ek idatzi zuen:
[...]
I do not know what would be the reasonable way to correct it: preventing
the shifting, or changing how highlighting interpret beginning of lines,
in case of Org?
I have the following in my emacs init file to prevent
Bastien writes:
I suggest you handle this the way you prefer: either by committing
this in Org before asking emacs-devel@, or by asking first then see
of this needs to be fixed upstream? I won't have time to digg this
issue further, sorry.
I'll just keep the patch locally for the moment, at
Bastien writes:
Feel free to install it, thanks!
Applied to master.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
Hi Tom,
Could you provide a minimal example? I'm unable to debug from the stack
trace alone.
Thanks,
t...@tsdye.com (Thomas S. Dye) writes:
Aloha all,
With a recent pull, Lisp code blocks that I'm fairly certain were
working previously started to fail. There is a backtrace below. The Lisp
Jarmo Hurri jarmo.hu...@syk.fi writes:
Rick Frankel r...@rickster.com writes:
Greetings again.
Again, the solution is to globally set the :hline property to =yes=
instead of the default =no=, and you will get the results you want.
The issue I am trying to raise here is the consistency of
I agree completely. So my question boils down to this feature request:
Now, that #+call lines can be named, would it be possible to reference
the results the same way as for code blocks?
I just pushed up a commit which should make this possible. E.g.,
* call by name
#+name: echo-input
On 2013-11-13 09:17, Eric Schulte wrote:
Perhaps we should change `org-babel-default-inline-header-args' to
include `(:hlines yes)'. If there is no push back on that change I'd
be happy to make it.
I agree. It would probably make the behavior less confusing.
rick
Eric-
Since you're looking at call lines :)...
there is a (fairly new i think) bug:
When searching forward for results, following call lines are not
being respected as stop points. For instance, given:
#+BEGIN_SRC org
,* Call block test
,#+name: call-me
,#+BEGIN_SRC emacs-lisp :var v=one
v
i have not been able to track this down further. has anybody taken a
look at it?
On 8/27/13, Samuel Wales samolog...@gmail.com wrote:
org-refile makes ido think that every entry that is in the
current buffer is a directory, while every entry that is
in another buffer is a file.
===
You
* computer
** emacs
*** myorg
I use ido.
===
i refile to myorg with the string myorg as an ido selector
i save all files
i refile to emacs
i take a look before pressing ret
ido shows me the wrong olpath
it shows me myorg with the filename in parentheses after
i wanted emacs
the next
Hi Bastien
On Wed, Nov 13, 2013 at 6:34 PM, Bastien b...@gnu.org wrote:
Please send me your public key and I'll give you write access.
It works, thank you. I have pushed my patch myself now. When and how often is
http://orgmode.org/manual/References.html
updated?
Michael
Dear org-mode team.
Hi
org-mode is gread major mode in my emacs life.
But, If this org-file is export to HTML, an indent will collapse.
I wish keep indents...
Best regards.
test.org
* Sample A
#+BEGIN_SRC C++
#include Eigen/Core
// Good layout.
// The indent is maintained.
int main()
nil might be a safer default?
On 11/13/13, Karl Voit devn...@karl-voit.at wrote:
(setq org-agenda-search-headline-for-time nil) should do.
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. ANYBODY can get it.
Denmark: free
Hi Eric,
Eric Schulte schulte.e...@gmail.com writes:
I agree completely. So my question boils down to this feature request:
Now, that #+call lines can be named, would it be possible to reference
the results the same way as for code blocks?
I just pushed up a commit which should make
Hello world,
I'm just taking another look at org-contacts. I wonder what the best
practice is for dealing with multi-line properties like postal
addresses.
I can just make them part of the entry, of course, not in a property,
but that seems oddly different from the other properites.
Have I
Package: org-mode
cus-test.el suggests the following variables may have incorrect
custom :types. (There may be some false positives.)
This refers to Org mode in current Emacs trunk.
Eg, org-texinfo-filename does not have nil as an option.
org-agenda-deadline-leaders
Hi all,
since my update just a few minutes ago, I have problems exporting one of
my documents to odt.
The new behaviour is, that I get asked
,
| Buffer foo.org22 modified; kill anyway? (yes or no)
`
Regardless of my answer after that, a new (empty) buffer is opened,
which has the name
Hi! I am using the latest org from git and I can't get org to export (I
need LaTeX export particularly) files with smart quotes.
The following example silently fails to produce smart quotes:
#+OPTIONS: ':t
#+LANGUAGE: ru
This is a 'test' file.
* Headline with 'quotes'
** Subheading with quotes.
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Hi all,
since my update just a few minutes ago, I have problems exporting one of
my documents to odt.
The new behaviour is, that I get asked
,
| Buffer foo.org22 modified; kill anyway? (yes or no)
`
Regardless of my answer
Hi Eric,
#+begin_src lisp
(+ 1 1)
#+end_src
Debugger entered--Lisp error: (wrong-type-argument listp 2)
byte-code(\211A@)\207 [result x] 2)
org-babel-execute:lisp((+ 1 1) ((:comments . ) (:shebang . ) (:cache .
no) (:padline . ) (:noweb . yes) (:tangle . no) (:exports . code)
(:results .
I did some brute force bug tracking and manage to track down the problem.
I made two different files:
test1.org:
#+TITLE: Test 1
#+OPTIONS: toc:nil
#+INFOJS_OPT:
* Header 1
* Header 2
** Subheader 2.1
test2.org:
#+TITLE: Test 1
#+OPTIONS: toc:nil
* Header 1
* Header 2
** Subheader 2.1
Hi Daniil,
Daniil Frumin difru...@gmail.com writes:
Hi! I am using the latest org from git and I can't get org to export (I
need LaTeX export particularly) files with smart quotes.
You need to add it to the variable org-export-smart-quotes-alist
defined in ox.el. Put your cursor on the
Hi Michael,
Michael Brand michael.ch.br...@gmail.com writes:
On Wed, Nov 13, 2013 at 6:34 PM, Bastien b...@gnu.org wrote:
Please send me your public key and I'll give you write access.
It works, thank you. I have pushed my patch myself now.
Thanks.
When and how often is
Samuel Wales samolog...@gmail.com writes:
nil might be a safer default?
This small feature would not be easily discovered if this option is
turned to nil, so I'd say `t' makes sense here.
But I don't feel strongly about this.
--
Bastien
Nishiyama Nobuyuki nishiy...@target-ent.com writes:
Dear org-mode team.
Hi
org-mode is gread major mode in my emacs life.
But, If this org-file is export to HTML, an indent will collapse.
I wish keep indents...
I cannot reproduce it: the two code blocks render identically in my
test.
Hi Samuel,
Samuel Wales samolog...@gmail.com writes:
I use ido.
I don't use ido so it's hard for me to mentally picture the problem
correctly.
Anyway, the error message was wrong in many circumstances, e.g. when
the user tries to refile and only mention the headline/, not the
target file.
Thank you.
Please note that the fact that it errors instead of refiling is a bug,
even if the error message is more accurate.
On 11/13/13, Bastien b...@gnu.org wrote:
Hi Samuel,
Samuel Wales samolog...@gmail.com writes:
I use ido.
I don't use ido so it's hard for me to mentally picture
Samuel Wales samolog...@gmail.com writes:
Please note that the fact that it errors instead of refiling is a bug,
even if the error message is more accurate.
In the cases I have in mind (which are probably not the same than
yours), the target file is unspecified and refiling cannot happen
I suspect it is the arguments used for ido.
I previously reported that Org incorrectly treats the current file
differently from other files. This causes ido to think that some
olpaths are files and others are directories. This might be related.
On 11/13/13, Bastien b...@gnu.org wrote:
In the
This also actually corrupts the buffer by inserting footnotes at the
end. Sometimes it leaves it in a narrowed state.
Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
goto-char(nil)
(progn (goto-char link-end) (skip-chars-forward ))
(setq post-blank (progn
I am still getting ellipses upon isearch, despite setting all relevant
variables to show the entire hierarchy, siblings, etc. Can isearch
reveal canonically?
Thanks.
Hi Tom,
That example works for me. Perhaps you could edebug (C-u C-M-x) the
`org-babel-execute:lisp' function and then run that code block again to
see at which statement the error is thrown.
I'm not sure what the problem could be.
Best,
t...@tsdye.com (Thomas S. Dye) writes:
Hi Eric,
Fixed, thanks for reporting.
Rick Frankel r...@rickster.com writes:
Eric-
Since you're looking at call lines :)...
there is a (fairly new i think) bug:
When searching forward for results, following call lines are not
being respected as stop points. For instance, given:
#+BEGIN_SRC org
Rick Frankel r...@rickster.com writes:
On 2013-11-13 09:17, Eric Schulte wrote:
Perhaps we should change `org-babel-default-inline-header-args' to
include `(:hlines yes)'. If there is no push back on that change I'd
be happy to make it.
I agree. It would probably make the behavior less
72 matches
Mail list logo