1. GNU Emacs 25.0.95.1 (i686-w64-mingw32) of 2016-06-13
2. org-20160704
#+BEGIN_COMMENT
(let ((buffer-name "*Test*"))
(with-output-to-temp-buffer buffer-name
(set-buffer buffer-name)
(when (featurep 'org)
(org-mode))
(setq truncate-lines 1)
(setq cursor-type nil)
(inse
Hello,
Spencer Hill writes:
> C.f. this emacs.stackexchange question:
> http://emacs.stackexchange.com/q/24313/8818
>
> As of version 8.3 of org, numbering of subtrees in export can be
> toggled via the :UNNUMBERED property. This applies to subheadings
> regardless of their own :UNNUMBERED prop
> but in things like font-lock it seems slow compared to a
> regexp. I have not found a reliable regexp approach though. say
> I want to search back for "cite:" with point at the ^ position
> below:
> some text cite:a-key
> ^
> If I run (re-search-backward "cite:") at the point above,
Robert Klein writes:
> are those Patches still being worked on?
Yes, but they haven't been pushed yet.
Rasmus
--
May the Force be with you
Nicolas Goaziou writes:
>> I'm not sure what were the conclusions of the side discussion, but
>> I do want to point out that my change is in accordance with unicode
>> symbol names and with the symbols that pdflatex prints on paper.
>
> I think Rasmus (Cc'ed) discovered a bug in TeX input method.
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Maybe a defcustom consisting of an alist of anonymous faces:
>>
>> '((R ((:background "red")))
>> (emacs-lisp ((:background "blue"
>
> Sounds good, even if a string as the key might be better (languages are
> stored as strings in the
Haustedt, Jens writes:
> Given this setting:
>
> some more text cite:a-key some text cite:a-key
> ^
> When you run (re-search-backward "cite:") at the point above, the result is
> as follows:
>
> some more text cite:a-key some text cite:a-key
>
Hello,
Rasmus writes:
> Sure, I can do that.
Thanks !
Regards,
--
Nicolas Goaziou
Hello,
I try to put some source code, using the listings package in my slides:
** Source Code
#+BEGIN_LATEX
\begin{lstlisting}
for (int i = 1; i != 10; ++i)
std::cout << i << ": hello, world!"
<< std::endl;
\end{lstlisting}
#+END_LATEX
Problem is, this, in contrast to
#+BEGIN
I found some difficulties with the org-link-set-parameters you suggested
Nick. Your version doesn't let you add properties to links with no
existing properties, e.g. ("http") and it also didn't work as expected
to set properties to nil. The current function is one you didn't like
earlier with setf
All,
I added group tags to org-tag-alist.
(:startgrouptag . nil)
("▸_NEW_SKILL" . ?\3)
("✔_OFF_CASE_PLAN" . ?\4)
("✘_LEFT_FIELD" . ?\5)
(:endgrouptag . nil)
When I used mobile org, about when it was generating indices, it
displayed the following message:
org-mobile-cre
On Tue, 5 Jul 2016, Joon Ro wrote:
Hi,
I'm aware of passing variables through header arguments, and also
inserting another source code block using the noweb syntax.
I was wondering, however, would it be possible to directly input values
of properties inside source code blocks? For example,
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
--
Nicolas Goaziou writes:
> It isn't a bug actually.
>
> Spreadsheet formulas are sent to Calc (unless it starts with "'(" in
> which case it is treated as Elisp). Doing symbolic computations, Calc
> parses "1d" as one time the symbolic variable "d". So "1d" is the same
> as "d".
>
> Basically, the
> Yes. `org-property-values' does the trick
>
>
> * Subtree
> :PROPERTIES:
> :DUMMY: Value
> :END:
>
> #+BEGIN_SRC shell :var dumdum=(car (org-property-values "DUMMY"))
> echo $dumdum
> #+END_SRC
>
> #+RESULTS:
> : Value
>
> #+NAME: get-property
> #+BEGIN_SRC emacs-lisp :var prop="prop"
> (or
Hello,
Rares Vernica writes:
> Just to clarify, how would you fix this:
>
> | [2016-07-05 Tue]--[2016-07-06 Wed] | 1d | vsum(d) |
> | [2016-07-06 Wed]--[2016-07-07 Thu] | 1d | 2 d |
> #+TBLFM: $3=vsum(@1$-1..@0$-1)
>
> Notice the "vsum(d)" instead of the expected "1 d". How would you add
> "
Hello,
Fabrice Popineau writes:
> Am I alone to see this recently:
>
> insert an src python block with moving inside the src block
> and then some timer function breaking with:
>
> Debugger entered--Lisp error: (wrong-type-argument symbolp #[128 "\300\301
> \"\206 ... [eldoc-documentation-funct
Hello,
Florian Lindner writes:
> How can I add a fragile option to the frame
You can set :BEAMER_OPT property accordingly.
> or make the BEGIN_src block use the lstlisting environment?
See `org-latex-listings'.
Regards,
--
Nicolas Goaziou
Hello,
"Francis J. Monari, Esquire" writes:
> = Is there any down-side to this patch? (My knowledge of LiSP and Org
> is very limited.)
> = If appropriate, can the source code be patched?
First, could you try Org development version and see if this bug is
fixed?
Thank you.
Regards,
--
Nico
2016-07-06 22:41 GMT+02:00 Nicolas Goaziou :
> Hello,
>
> Fabrice Popineau writes:
>
> > Am I alone to see this recently:
> >
> > insert an src python block with > moving inside the src block
> > and then some timer function breaking with:
> >
> > Debugger entered--Lisp error: (wrong-type-argume
Fabrice Popineau writes:
> The problem is that the byte code comes from Python mode.
> I solved the problem with this:
>
> $ diff -uw contrib/lisp/org-eldoc.el contrib/lisp/org-eldoc.el
> --- contrib/lisp/org-eldoc.el 2016-02-29 11:13:22.330099500 +0100
> +++ contrib/lisp/org-eldoc.el 2016-07
Hello,
John Kitchin writes:
> Your version doesn't let you add properties to links with no
> existing properties, e.g. ("http")
There was a typo (spurious `cdr'), the correct version is
(defun org-link-set-parameters (type &rest parameters)
"Set link TYPE properties to PARAMETERS.
PARA
Thanks. I responded to some below. I didn't respond to all of them. I
will revise the commits accordingly and send a new version.
Nicolas Goaziou writes:
> Hello,
>
> John Kitchin writes:
>
>> Your version doesn't let you add properties to links with no
>> existing properties, e.g. ("http")
>
>
On Wed, 6 Jul 2016, Joon Ro wrote:
Yes. `org-property-values' does the trick
* Subtree
:PROPERTIES:
:DUMMY: Value
:END:
#+BEGIN_SRC shell :var dumdum=(car (org-property-values "DUMMY"))
echo $dumdum
#+END_SRC
[deleted]
Thank you so much for the reply - this would be very useful. Would
Hello!
I have an Org document that does several SQL queries against two different
PostgreSQL databases. Currently I set the =:dbhost= header argument for each
source block, like this:
#+BEGIN_SRC sql :dbhost db1.example.com
SELECT 1;
#+END_SRC
#+header:
#+BEGIN_SRC s
I think I have addressed these. Revised commits appended and at
https://github.com/jkitchin/org-mode/tree/link-9.0-v3.
The new org-link-set-parameters function you suggested works fine as far
as I can tell. WDYT?
commit f8bb180150514b92535506601c747001da305610
Author: John Kitchin
Date: Tue J
> I have no idea what you are asking.
>
> > The reason is I have to put those values inside a comment,
> > so I cannot pass them as variables.
>
> So your original query about accessing property values from src blocks was
> not what you wanted?
>
> Examples of what one is trying to do - eve
Hi Rares
On Mon, Jul 4, 2016 at 6:28 PM, Rares Vernica wrote:
> | [2016-07-03 Sun]--[2016-07-04 Mon] | 1d | d |
> | [2016-07-03 Sun]--[2016-07-05 Tue] | 2d | 2 d |
> #+TBLFM: $3=$2
A Calc formula interprets field values as a symbolic expressions to
calculate with. To copy literally one needs
28 matches
Mail list logo
