Rick Frankel 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 the system,
not the way to solve this particular problem. P
Hi, Org people. Just observing this little nit.
If I insert an email message (copy and pasted from Gnus in my case)
within:
#+BEGIN_SRC mail
#+END_SRC
the header lines of the message are highlighted with a reasonable set of
colors. However, with the cursor within the message, I hid "C-c
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
code executes correctly, but Babel doesn't appear to get the results in
the form it expects (if I'm reading the backtrace correctly).
Have I mucked
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 can do something like:
#+BEGIN: propview :id " myt
Aloha all,
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 intended?
* Folded heading ...
[dead space]
[dead
Oops; forgot to reply-all. Aaron's advice did set me straight, and #+CALL: is
working fine for me now without my ill-advised debugging artifacts. Thanks to
Aaron for the assistance, and to the Org list/maintainers for all the great Org
tools and documentation.
Phil
- Original Message ---
Thank you for the clarification Eric. That did exactly what I wanted it to!
Best,
Stephen
e.fr...@ucl.ac.uk writes:
> "Stephen J. Barr" writes:
>
>> I agree with the "less stuff" part. The first pass in my slides is for
>> content, second pass is for formatting :-). For now, I did manual divisi
Hi Phil,
I’m far from an expert myself, but I think I see what is going on with
your testcases.
2013ko azaroak 12an, Phil Regier-ek idatzi zuen:
[...]
> *Once* I got output, but I could not reproduce this after making and
> undoing a few formatting changes; I would chalk this up to my own
> clu
I'm new to Babel -- I've been using Org for the last few years just to organize
and typeset simple LaTeX for PDF and MathJax export -- and furthermore have had
to compile Emacs from scratch and install into my home directory (installing
Org as an ELPA package) to get my versions to sync up with
Achim Gratz writes:
> Introduced with r114064 on Emacs trunk. Not sure if this is a bug in
> Org or Emacs, but the patch restores the previous behaviour.
> ---
> lisp/ob-ref.el | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/lisp/ob-ref.el b/lisp/ob-ref.el
> index 5a3
Hi Kenneth,
Kenneth Jacker writes:
> Great minds think alike? ;-)
>
> That's what I ended up using soon after my ML posting.
Great manual make great minds stumble upon solutions :)
> bzg> but the presence of the repeater will still let the TODO state
> bzg> switch to the next one, namely
[resent]
Bastien writes:
> Thanks -- I remember we had this issue before. I'm just surprise I'm
> the first one to report it, I assume many people use a recent Emacs
> with macro expansion done this way.
This patch fixes the error, but it looks strange (indentation is still
unchanged for clarity
Achim Gratz writes:
> Here's a better patch (I hope).
Feel free to install it, thanks!
--
Bastien
Hi Gregor,
Gregor Kappler writes:
> When drawers are hidden this wastes three lines of screen real estate
> : * heading
> : :LOGBOOK:...
> : :CLOCK:...
> : :PROPERTIES:...
> per line.
>
> I adapted org-flag-drawer to hide the newlines as well if another drawer
> is following:
> : * heading
> : :
Hi Aaron and Tod,
Aaron Ecay 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 (org-element-at-point)) '(src-block
> example-block ...)))
>
> A
Hi Tod and Bastien,
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 the headline (as can be
conf
bzg> Hi Kenneth,
Hello, Bastien!
Sorry to have taken so long to reply ...
>> When I use `t' or "C-c C-t", the keywords change from TODO, to PENDING,
>> to CANCELED, and then repeat *only those three states*.
>>
>> Shouldn't I be able to use the above to mark the this week's task as DO
Rasmus writes:
> Rasmus writes:
>
>> If anyone can figure out what is wrong on the Org side or what "broke"
>> in Emacs-Core it would be great! "Luckily" it's an all-C commit so I
>> don't know how to proceed from here. . .
>
> This really stupid patch allows me to export the document I was unabl
To: emacs-orgmode@gnu.org
Subject: Bug: Debugger entered--Lisp error: (invalid-function
org-with-silent-modifications) despite reinstall [8.2.3a (8.2.3a-elpaplus @
c:/Users/Dexter/.emacs.d/elpa/org-plus-contrib-2013/)]
From: odta...@yahoo.com
--text follows this line--
Remember to cover the b
Bastien,
When there is no property drawer before the code block, C-c C-x p
affects the code block and either doesn't create a property drawer or it
leaves the 'real' property drawer unaffected.
An example for the second case, where org-set-property matches the code
block, despite an existing prope
Often several consecutive drawers follow the headline in my setup.
Maybe this code to hide newlines after drawers is of some use.
When drawers are hidden this wastes three lines of screen real estate
: * heading
: :LOGBOOK:...
: :CLOCK:...
: :PROPERTIES:...
per line.
I adapted org-flag-drawer to
Rasmus writes:
> I bisected emacs-bzr to find the revision where it breaks for me
> (cf. attached test case). It's this one:
>
> committer: Dmitry Antipov
Please report this as an Emacs bug. I can find no bug that this change
is fixing and it clearly alters (undocumented, AFAICS) behaviour,
On 2013-11-12 11:09, Jarmo Hurri wrote:
Rick Frankel writes:
Greetings Rick.
Note that in versions of org-mode prior to commit 6857d139 of
2013-09-28 (below), this was overridden in the setting of
`org-babel-default-header-args:emacs-lisp, so this may be why you are
seeing and "inconsistency"
Rasmus writes:
[...]
> This really stupid patch allows me to export the document I was unable
> to export yesterday with emacs-bzr r115062 (latest or almost latest)
> and the latest version Org.
>
> Eric F., would you mind testing it with your slides?
I've tested it with three files, one a beam
Hi,
This used to work, back in August but I just updated today and Something
Has Changed.
After setting this option:
(setq org-link-abbrev-alist '(("att" . org-attach-expand-link)))
It was possible to insert a link to an attachment like this:
[[att:FigureA.jpg]]
and clicking on it would show
Rick Frankel writes:
Greetings Rick.
> Note that in versions of org-mode prior to commit 6857d139 of
> 2013-09-28 (below), this was overridden in the setting of
> `org-babel-default-header-args:emacs-lisp, so this may be why you are
> seeing and "inconsistency" between the call line and the ema
Hi Thomas,
Thomas Morgan writes:
> I'm afraid I'm still seeing the same behavior described
> in the bug report.
You're right, there are still annoying bugs after filtering.
I'll have a look when I have more time at hand.
Best,
--
Bastien
On 2013-11-12 01:16, Jarmo Hurri wrote:
Eric Schulte writes:
There are two paces to specify header arguments in a call line, the
arguments in the [] are applied to the input-table function, *not* to
the call line, so they change the inputs. The trailing header
arguments are applied to the call
Hi, Bastien,
Thanks for giving this your attention.
I'm afraid I'm still seeing the same behavior described
in the bug report.
Best,
Thomas
Bastien writes:
> Hi Nick,
>
> Nick Dokos writes:
>
>> ISTR that Jay had parentheses around org-html-publish-to-html in his
>> template, thereby making it (wrongly) into a function call. Somebody (don't
>> remember who, sorry) pointed that out but maybe it's worth bringing it
>> up again.
>
> Ye
Am 11.11.2013 17:58, schrieb Bastien:
> Hi Rainer,
>
> Rainer Stengele writes:
>
>> That might be a bug.
>
> Did you re-compile Emacs recently? This looks like a bug in the
> display engine that I've noticed too a while ago.
>
Hi Bastien,
no, I use "GNU Emacs 24.3.50.1 (i386-mingw-nt6.1.7601
Hi Nick,
Nick Dokos writes:
> ISTR that Jay had parentheses around org-html-publish-to-html in his
> template, thereby making it (wrongly) into a function call. Somebody (don't
> remember who, sorry) pointed that out but maybe it's worth bringing it
> up again.
Yep, I remember Robert Klein sugg
Bastien writes:
> Hi Jay,
>
> Jay Dixit writes:
>
>> Thanks. I disabled smex, and now when I m-x org-publish, I get:
>>
>> Publishing file /Users/jay/blog-test/my-blog.org using
>> `org-html-publish-to-html'
>> org-html-publish-to-html: Wrong number of arguments: #[(format plist
>> filename pub
Hi Tod,
Tod Middlebrook writes:
> Is it a trivial fix to alter drawer and possibly other element regexps
> to never match anything inside of a code block, or should I add it to
> http://orgmode.org/tmp/worg/org-issues.html ?
It is not trivial, but your best chance is to describe the bug on this
Bastien,
I apologize for the mishaps of sending from the wrong address that time
and for somehow leaving off the commentary that I thought was sent with
the code block.
Is it a trivial fix to alter drawer and possibly other element regexps
to never match anything inside of a code block, or shou
Rasmus writes:
> Rasmus writes:
>
>> If anyone can figure out what is wrong on the Org side or what "broke"
>> in Emacs-Core it would be great! "Luckily" it's an all-C commit so I
>> don't know how to proceed from here. . .
>
> This really stupid patch allows me to export the document I was una
"Stephen J. Barr" writes:
> I agree with the "less stuff" part. The first pass in my slides is for
> content, second pass is for formatting :-). For now, I did manual division
> of the sides. I am using both org-beamer and org-reveal (
> https://github.com/yjwen/org-reveal) and ideally they would
37 matches
Mail list logo
