John Kitchin writes:
> thanks for the report. I think I have fixed it in a recent push.
It now gets the bibtex entry right however its behaviour is strange: it
asks twice for a file name to save. The first query seems ok but if you
give again the bib file as argument the second time, you get a w
Hello,
when exporting to LaTeX, numbers expressed in engineering notation
contained in tables are transformed into a quite confusing notation:
1.234e5 becomes 1.234\,(5) which is rendered by LaTeX as 1.234 (5) with
the space being a very narrow one. This notation is confusing because it
is usually
i'd like to make org-link-minor-mode toggleable in ediff. is this
possible? i tried in the b buffer and in the control panel, and it
did not take effect.
thanks.
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
The disease DOES progress. MANY people have died from it. And
ANYBODY
Adam Porter writes:
> Hi again Eric,
>
> On second thought, while symlinks may be worth trying, they might not work.
> I've noticed similar issues using Dropbox.
>
> If you put the file in your git repo and the symlink in Syncthing's repo,
> I'm guessing Syncthing will not follow the symlink, in
Hi again Eric,
On second thought, while symlinks may be worth trying, they might not work.
I've noticed similar issues using Dropbox.
If you put the file in your git repo and the symlink in Syncthing's repo,
I'm guessing Syncthing will not follow the symlink, in which case it
wouldn't sync the c
Hi Eric,
Sorry I'm late, just thought I'd share an idea: did you try symlinks? A
symlink points to a path, not an inode, so it shouldn't get broken like a
hard link.
Hi
I have an org file with reference controlled by org-ref.
The bib entry in the corresponding bib files contains a note field.
When exporting the org file to latex, everything is as expected. (I have
to run bibtex anyhow). But when I export to html the note field does not
appear. Is this a know
>>> "Nicolas" == Nicolas Goaziou writes:
> Hello,
> Uwe Brauer writes:
>> However when I try to export a org file with a table controlled by
>> table.el I run into a problem. I have to convert it to a org-table and
>> in this process things like splitting cells are lost.
Hello,
Jonas Bernoulli writes:
> The related `org-texinfo--build-menu' has a similar issue. Unlike
> `org-texinfo-make-menu' which may end up not inserting a newline
> when it should, it may end up removing a newline when it should not.
>
> Given this Org file:
>
> #+TITLE: Demo2 Manual
> #
Hello,
Jonas Bernoulli writes:
> Given this Org file
>
> #+TITLE: Demo Manual
> #+TEXINFO_DIR_CATEGORY: Emacs
> #+TEXINFO_DIR_TITLE: Demo: (demo).
> #+TEXINFO_DIR_DESC: Demo.
>
> * Missing empty line
>
> There is text between the heading and the menu
>
> ** There is text b
Hello,
Uwe Brauer writes:
> However when I try to export a org file with a table controlled by
> table.el I run into a problem. I have to convert it to a org-table and
> in this process things like splitting cells are lost.
Why do you have to do that? Could you show an ECM?
> So could org-expo
Daniele Pizzolli writes:
> Thanks Nicolas for the reply. Ok, but `org-babel-execute-buffer'
> produces an inconsistent document right now.
This is because you ask it to. See below.
> Mmm, the same reasoning can be used for arguing about the current
> behaviour: If I C-c C-c on a block, I expec
The related `org-texinfo--build-menu' has a similar issue. Unlike
`org-texinfo-make-menu' which may end up not inserting a newline
when it should, it may end up removing a newline when it should not.
Given this Org file:
#+TITLE: Demo2 Manual
#+TEXINFO_DIR_CATEGORY: Emacs
#+TEXINFO_DIR_TIT
Hello
Given this Org file
#+TITLE: Demo Manual
#+TEXINFO_DIR_CATEGORY: Emacs
#+TEXINFO_DIR_TITLE: Demo: (demo).
#+TEXINFO_DIR_DESC: Demo.
* Missing empty line
There is text between the heading and the menu
** There is text before this menu
** the empty line before Menu IS
Hi Nicolas,
I don’t believe it was ever applied, nor was it superseded by another. This was
to fix a problem with testing older versions of git-annex. I believe David
remove git-annex on the buildbot, which stopped it from failing, because it was
not being tested.
If you need me to make any chang
Hi,
Here is my proposal to create a new :async feature for
Org-babel-clojure. This is discussed at length in this blog post:
http://fgiasson.com/blog/index.php/2016/04/05/using-clojure-in-org-mode-and-implementing-asynchronous-processing/
I added the commit of the changes, the commit for the
I'm sorry, I only just understood, from looking at git, that you added the
ability to use angular links inside link descriptions in response to my
query.
Thanks very much for this quick fix! I look forward to the next release.
On 6 April 2016 at 10:43, Reuben Thomas wrote:
> On 6 April 2016 at
I used to be able to use org-buffer-org-mime-htmlize to send my org documents
as multipart/alternative html & text email. For some
reason, this is stopped working, and now displays
Unknown "nil" back-end: Aborting export
In the *Messages* buffer, I see
org-export-barf-if-invalid-backend: Unkno
Oh, right. I should attach it.
```diff
>From 30eec5a63e4f720fa3880b9aef06aedd84072078 Mon Sep 17 00:00:00 2001
From: stardiviner
Date: Sat, 2 Apr 2016 00:46:36 +0800
Subject: [PATCH] add SLY support in ob-lisp
* ob-lisp.el (org-babel-execute:lisp): Support using SLY to evaluate
lisp src block.
Hi Nicolas!
-;;; ob-clojure.el --- Babel Functions for Clojure-*- lexical-binding: t;
-*-
+;;; ob-clojure.el --- org-babel functions for clojure evaluation
Your patch reverts a change introduced in development version. Could you
rebase it on top of latest Org first?
Yeah sorry, I did thi
On Wednesday, 6 Apr 2016 at 15:21, Nicolas Goaziou wrote:
> In the second case, something is preventing =xxx= from being parsed as
> a verbatim object.
Ah, I see. Makes perfect sense. Thanks.
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-705-g716e33
On Wednesday, 6 Apr 2016 at 14:46, Nicolas Goaziou wrote:
> FWIW, I cannot reproduce it.
Ignore. Probably due to the same issue discussed elsewhere: my
modification of org-emphasis-alist...
thanks!
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-705-g716e33
On Wed, Apr 06 2016, Nicolas Goaziou wrote:
> Hello,
>
> Daniele Pizzolli writes:
>
>> is possible to update the “#+RESULTS: pid” when the block “#+NAME:
>> echo-pid” is evaluated in the following snippet?
>
> Without `org-babel-execute-buffer', I don't think so.
Hello,
Thanks Nicolas for the r
hi
It is great that in orgmode I can edit tables, which are controlled by
table.el, since table.el for example allows to split and joins cells,
which org-table does not.
However when I try to export a org file with a table controlled by
table.el I run into a problem. I have to convert it to a or
Eric S Fraga writes:
> However, I am curious as to why the output from the inline source
> evaluation is different? I.e. why =xxx= versus xxx? What is the
> rationale for one versus the other?
The result of the inline source evaluation is =xxx= (I'll ignore the
no-op results macro around it).
On Wednesday, 6 Apr 2016 at 14:37, Nicolas Goaziou wrote:
> Wild guess. You forbade ":" after emphasis markers in
> `org-emphasis-regexp-components'.
Ummm, I've never touched org-emphasis-regexp-components...
But I have played around with org-emphasis-alist, introducing @ as an
emphasis marker (
Hello,
Erik Hetzner writes:
> * lisp/org-attach.el (org-attach-annex-get-maybe): Use relative path as
> argument for git annex. Fixes error in test with version 3 of git
> annex.
It seems like I lost track on this one. Could you tell me about the
status of this patch? I doesn't seem to be a
Hi,
Yes, you are. There is a "go to the topic" action on the left panel.
Anyway, there is not much to see, just some pointers to start
a discussion.
Haa great thanks, see it now :)
Let me revise a few things, suggest another patch, and then will start
to think about these things.
Thanks,
Frederick Giasson writes:
> Humm, from the page you provided, I don't see any threads, but just
> the initial message, am I looking at the right thing?
Yes, you are. There is a "go to the topic" action on the left panel.
Anyway, there is not much to see, just some pointers to start
a discussion.
Hi Nick.
[...]
>> Excuse me if this sounds almost philosophical, but in which situation an
>> indirect buffer may be better that just focusing on the same (original)
>> buffer? For example, when you are toying with potentially big
>> modifications and don't want to replace the original? Is it like
Hi Adam. Porter writes:
>> Excuse me if this sounds almost philosophical, but in which situation an
>> indirect buffer may be better that just focusing on the same (original)
>> buffer? [...]
> [...]
> So by jumping to an entry in an indirect buffer, I see only that entry, and
> I can't modify
Hi Nicolas,
However, I am not sure neither how generic such a solution could be,
and what would still be required to implement in each OB plugin. My
(very little) experience so far is the Python prototype that John
wrote, and then my analysis of the Clojure OB plugin. As I was
explaining in this
Hello,
Daniele Pizzolli writes:
> is possible to update the “#+RESULTS: pid” when the block “#+NAME:
> echo-pid” is evaluated in the following snippet?
Without `org-babel-execute-buffer', I don't think so.
> This will lead to a consistent document generation with “M-x
> org-babel-execute-buffe
Hello,
"numbch...@gmail.com" writes:
> Hi, Nicolas, the another email which you commented many places is outdated.
> That patch is modified from the version of MELPA package `org-plus-conrtib`.
>
> I cloned org-mode git repo, and created public repo branch at here:
> https://github.com/stardivin
Hello,
Eric S Fraga writes:
> I have the following macro to aid in presenting calculations in
> solutions to coursework questions etc. for my teaching:
>
> #+macro: calculate src_calc[:exports code]{$1} = @@latex:\fbox{@@
> src_emacs-lisp{(setq var-$2 (string-to-number (calc-eval "evalv($1)")))
Hello,
Frederick Giasson writes:
> However, I am not sure neither how generic such a solution could be,
> and what would still be required to implement in each OB plugin. My
> (very little) experience so far is the Python prototype that John
> wrote, and then my analysis of the Clojure OB plugin
Hello,
Eric S Fraga writes:
> Could anybody explain why these two lines give different outputs for the
> inline elisp calculation?
>
> First line:
>
> @@latex:\fbox{@@ src_emacs-lisp{(setq var-Q1 (string-to-number (calc-eval
> "evalv(15.357*(184.2-80))")))} @@latex:}@@
>
> Second line:
>
> @@la
Could anybody explain why these two lines give different outputs for the
inline elisp calculation?
First line:
@@latex:\fbox{@@ src_emacs-lisp{(setq var-Q1 (string-to-number (calc-eval
"evalv(15.357*(184.2-80))")))} @@latex:}@@
Second line:
@@latex:\fbox{@@ src_emacs-lisp{(setq var-Q1 (string-
Hi Nicolas,
Here is a blog post that explains the changes I did. I still have one
improvement to do (but don't how it could be done or even if it can be
done) which is explained at the end of the post:
http://fgiasson.com/blog/index.php/2016/04/05/using-clojure-in-org-mode-and-implementing-asyn
Hello,
is possible to update the “#+RESULTS: pid” when the block “#+NAME:
echo-pid” is evaluated in the following snippet?
This will lead to a consistent document generation with “M-x
org-babel-execute-buffer” or by hitting “C-c C-c” on “#+NAME:
echo-pid”. Using the cache does not make sense: th
Hello,
I have the following macro to aid in presenting calculations in
solutions to coursework questions etc. for my teaching:
#+macro: calculate src_calc[:exports code]{$1} = @@latex:\fbox{@@
src_emacs-lisp{(setq var-$2 (string-to-number (calc-eval "evalv($1)")))} \to $2
@@latex:}\\@@
The "\t
Hi,
I just updated to the current 8.3.4 after a system upgrade (Mac OS X
10.11, fresh Emacs 24.5.1 installed via Homebrew).
When trying to =make up2=, I got 79 "unexpected" failures. About the
same as I recall from some months back, but far more than I used to. Are
other people getting this many
Hi, Nicolas, the another email which you commented many places is outdated.
That patch is modified from the version of MELPA package `org-plus-conrtib`.
I cloned org-mode git repo, and created public repo branch at here:
https://github.com/stardiviner/org-mode/tree/sly-support-for-ob-lisp
I check
On 6 April 2016 at 10:44, Nicolas Goaziou wrote:
> Reuben Thomas writes:
>
> > So the feature is not in 8.3.4?
>
> No it isn't. New feature are added to development branch (master, which
> will become Org 9.0 when ready), not stable branch.
>
Thanks again.
--
http://rrt.sc3d.org
Reuben Thomas writes:
> So the feature is not in 8.3.4?
No it isn't. New feature are added to development branch (master, which
will become Org 9.0 when ready), not stable branch.
Regards,
Hello,
Thank you for the patch.
Frederick Giasson writes:
> -;;; ob-clojure.el --- Babel Functions for Clojure-*- lexical-binding: t;
> -*-
> +;;; ob-clojure.el --- org-babel functions for clojure evaluation
Your patch reverts a change introduced in development version. Could you
rebase i
On 6 April 2016 at 10:35, Nicolas Goaziou wrote:
> Reuben Thomas writes:
>
> > When you say "latest Org", which version is that?
>
> The tip of master branch, a.k.a. development version. At the moment, is
> it "release_8.3.4-705-g716e33".
>
So the feature is not in 8.3.4?
thanks again,
Reube
Reuben Thomas writes:
> When you say "latest Org", which version is that?
The tip of master branch, a.k.a. development version. At the moment, is
it "release_8.3.4-705-g716e33".
Regards,
Hello,
"numbch...@gmail.com" writes:
> I original created an package ob-lisp on here:
> https://github.com/stardiviner/ob-lisp
> and add it to MELPA recipe.
> https://github.com/melpa/melpa/pull/3682
>
> The author suggest me to merge this change to Org-mode.
>
> I attached patch in attachment f
On 6 April 2016 at 10:13, Nicolas Goaziou wrote:
> Hello,
>
> Reuben Thomas writes:
>
> > \href{Starting\%20Workshop\%20Notes.org}{\url{Starting Workshop
> Notes.org}}
> >
> > But maybe the space ends the URL?
>
> Indeed. For obvious reasons, "plain links" do not accept spaces since
> those are
Hello,
"numbch...@gmail.com" writes:
> Ask a beside question. I cloned org-mode git repo, should I contribute my
> patch with git way? (I mean create a git branch on my own public clone,
> then paste it here to let maintainer merge it?)
Please look at the document suggested by Thomas. In partic
Hello,
"numbch...@gmail.com" writes:
> My think my patch modifies less than 15 lines. Do I have to assign the
> copyright of FSF?
No you don't. That will be helpful for your next patches.
> I have sent one. But no response for some days. I hope Org-mode maintainer
> can merge this patch.
The
Hello,
Reuben Thomas writes:
> \href{Starting\%20Workshop\%20Notes.org}{\url{Starting Workshop Notes.org}}
>
> But maybe the space ends the URL?
Indeed. For obvious reasons, "plain links" do not accept spaces since
those are used as a delimiter. However, angular links could be used in
this case
On 5 April 2016 at 23:01, Nicolas Goaziou wrote:
> Hello,
>
> Reuben Thomas writes:
>
> > The output for
> >
> > [[file:Starting%20Workshop%20Notes.org][file:Starting Workshop
> Notes.org]]
> >
> > is:
> >
> >
>
> \href{Starting\%20Workshop\%20Notes.org}{\url{Starting} Workshop Notes.org}
>
Hello,
Makmiller Pedroso writes:
> I am using Org-mode version 8.3beta (release_8.3beta-422-gb54ad3).
>
> I tried to create a minimal example in which the CLOCKSUMs do not get
> updated. It seems that the CLOCKSUM_T is the one that is not getting
> updated (unless if I run the column view in the
Hello,
Sharon Kimble writes:
> Being that we can have multiple cursors, is it possible to have 2
> separate, distinct, tasks being clocked both at the same time?
[...]
> So, can it be done please?
There can only be one active clock at any given time. Although
I understand the need for some s
Being that we can have multiple cursors, is it possible to have 2
separate, distinct, tasks being clocked both at the same time?
I've googled but didn't come up with anything, but trying it I find that
'Task B' when it starts timing it auto-logs-out of 'Task A'. But I'm now
in the situation where
Hello,
Frederick Giasson writes:
> Here is a blog post that explains the changes I did. I still have one
> improvement to do (but don't how it could be done or even if it can be
> done) which is explained at the end of the post:
>
> http://fgiasson.com/blog/index.php/2016/04/05/using-clojure-in-
Hello,
Ross Donaldson writes:
> So: by default (at least, for me, in my configuration), Org
> automatically tries to interpret the results of src blocks as Org
> values -- usually tables. For example, evaluating `ls -la` in a shell
> src block returns, by default, Org's best attempt to parse a t
59 matches
Mail list logo
