* ("Cannot open load file" "org-fstree") vs (babel, windows, shell)
long story short, fstree strategy leads to "cannot open load path", babel
route is only explained for I believe Linux version. Ad-hoc solution with
Windows command prompt, cut and paste directory structure.
** org tree iss
Nicolas Goaziou writes:
> Hello,
>
> Andreas Leha writes:
>
>> inline source -- when on its own line -- breaks the paragraph, which is
>> unexpected.
>>
>> Here is a test file:
>>
>> * Test
>>
>> This is a broken
>> src_R[:exports results :results raw]{10}
>> paragraph.
>>
>>
>> Here is (the rel
It sounds as though most people don't particularly care which shell is
used. However, I believe Greg is correct and the *right* thing to do is
to have specific names (bash, sh, etc...) denote specific shells. I'd
also like "#+begin_src shell" to specify the "don't care" option. That
is what thes
Achim Gratz writes:
> schulte.e...@gmail.com writes:
>> I think this change could make it easier to reproduce problems with
>> Org-mode loaded and without the user's personal config loaded.
>
> So you want $(BATCH) with "-batch" filtered out?
Essentially.
> You can do that without the code du
"Sebastien Vauban" writes:
> Hello Eric,
>
> Eric Schulte wrote:
>>> When results caching is enabled, and when the hash must be updated, the
>>> "meta-lines" in front of the results block are _deleted_.
>>
>> You should use a named code block if you want to decorate the results.
>
> No, as long a
Hi Eric,
Eric Schulte writes:
> This should work in a recent Emacs.
>
> (require 'json)
> (defun org-as-json-to-file (&optional path)
> "Export the current Org-mode buffer as JSON to the supplied PATH."
> (interactive "Fwrite to file: ")
> (let ((tree (org-element-parse
schulte.e...@gmail.com writes:
> I think this change could make it easier to reproduce problems with
> Org-mode loaded and without the user's personal config loaded.
So you want $(BATCH) with "-batch" filtered out? You can do that
without the code duplication.
> + --eval '(setq org-babel-l
Eric Schulte writes:
>> How about the following resolution? We rename ob-sh.el to ob-shell.el.
>> New "shell" code blocks could use the value of the
>> `org-babel-sh-command' environment variable. Then sh, bash, zsh, csh,
>> ash, dash (am I missing any other common ones) use the specific shell
>>
Dror Atariah writes:
> Managed to get [backtrace] output...
>
> You can find it here: https://gist.github.com/drorata/7950857
>
> I could not find my way in this output... :(
>
If you look at the top of the backtrace it shows this:
,
| Debugger entered--Lisp error: (wrong-type-argument seq
Hello,
Andreas Leha writes:
> inline source -- when on its own line -- breaks the paragraph, which is
> unexpected.
>
> Here is a test file:
>
> * Test
>
> This is a broken
> src_R[:exports results :results raw]{10}
> paragraph.
>
>
> Here is (the relevant part of) the output of the LaTeX export
On Dec 13, 2013, at 20:51 PM, Nick Dokos wrote:
> Dror Atariah writes:
>
>> On Dec 13, 2013, at 16:08 PM, Nick Dokos wrote:
>>
>>> Dror Atariah writes:
>>>
Today I realized that I cannot execute successfully 'org-mobile-push'. In
particular here is the output from '*Messages*':
>>
"Sebastien Vauban"
writes:
> Eric S Fraga wrote:
>> Andreas Davour writes:
>>>
>>> I've just started using gnus again, and since it seems like bbdb is in a
>>> messy state someone suggested I try org-contacts as an address book
>>> solution. It looks quite usable, but I have a few questions.
>>
Hello Eric,
Eric Schulte wrote:
>> When results caching is enabled, and when the hash must be updated, the
>> "meta-lines" in front of the results block are _deleted_.
>
> You should use a named code block if you want to decorate the results.
No, as long as the lines which I do insert between the
Dror Atariah writes:
> On Dec 13, 2013, at 16:08 PM, Nick Dokos wrote:
>
>> Dror Atariah writes:
>>
>>> Today I realized that I cannot execute successfully 'org-mobile-push'. In
>>> particular here is the output from '*Messages*':
>>>
>>> Creating agendas...
>>> Agenda written to Org file /Us
Renato writes:
> Hi,
> as I already told, I'm a really newbe (to org-mode, as well as emacs)
> I'm starting from the very beginning:
> following the Doc (here:
> http://orgmode.org/worg/org-tutorials/orgtutorial_dto.html)
> I wrote my firs TODO list.
> But when I press C-c C-t over a TODO element
You should use a named code block if you want to decorate the results.
Best,
"Sebastien Vauban" writes:
> Hello,
>
> When results caching is enabled, and when the hash must be updated, the
> "meta-lines" in front of the results block are _deleted_.
>
> Such meta-lines include:
> - ATTR_LaTeX li
On Dec 13, 2013, at 16:08 PM, Nick Dokos wrote:
> Dror Atariah writes:
>
>> Today I realized that I cannot execute successfully 'org-mobile-push'. In
>> particular here is the output from '*Messages*':
>>
>> Creating agendas...
>> Agenda written to Org file /Users/drorata/Dropbox/MobileOrg/ag
Eric Schulte writes:
>>
>> How about the following resolution? We rename ob-sh.el to ob-shell.el.
>> New "shell" code blocks could use the value of the
>> `org-babel-sh-command' environment variable. Then sh, bash, zsh, csh,
>> ash, dash (am I missing any other common ones) use the specific she
This should work in a recent Emacs.
(require 'json)
(defun org-as-json-to-file (&optional path)
"Export the current Org-mode buffer as JSON to the supplied PATH."
(interactive "Fwrite to file: ")
(let ((tree (org-element-parse-buffer)))
(org-element-map tree
Hi Nicolas,
I'm sorry for the late reply.
2013/12/3 Nicolas Goaziou :
> This should be fixed. Thank you for the detailed report.
Yes, I confirm that it's fixed now, thanks a lot! Though, I have
another problem: the `ltxpng/' directory isn't copied when publishing
the whole project. Do I need t
you need to put this in your init.el (or other configuration file) I think:
(setq org-log-done 'time)
or add this to the top of the org-file
#+STARTUP: logdone
John
---
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carne
Greg Troxel wrote:
> Eric Schulte writes:
>
>> Although purely semantically, in my opinion the "sh" in "#+begin_src sh"
>> indicates generic "shell-script", not the POSIX sh. E.g., there is no
>> ob-bash.el or ob-csh.el.
>
> I see your point. But stepping back, I have always felt that
> "#+begin
Hello,
Brett Viren writes:
> However this method only works for a very simple org document. I'm
> successfully filtering out the :parent properties of (most of) the
> elements but as soon as my document produces a plain text element like:
>
> #("Text" 0 4 (:parent #1))
>
> then two problems o
Matt Price writes:
> I am pretty ignorant and may have missed a referene o this in the
> thread, but this (very outdated) code is on the emacswiki:
>
> http://www.emacswiki.org/emacs/org-json.el
Thanks. My searches didn't find this. It looks like this is parsing
the org buffer directly and onl
Hello,
Laurens Van Houtven <_...@lvh.io> writes:
> I'm using org-mode with the LaTeX export to write a book. I'm having issues
> with inline LaTeX citations (\cite{some label}) and glossary references
> (\gls{some label}). When the label (the thing in between the curly braces)
> is split across l
Eric Schulte writes:
> Although purely semantically, in my opinion the "sh" in "#+begin_src sh"
> indicates generic "shell-script", not the POSIX sh. E.g., there is no
> ob-bash.el or ob-csh.el.
I see your point. But stepping back, I have always felt that
"#+begin_src foo" referred to a langu
Hi,
Nicolas Goaziou writes:
> You can walk the tree, e.g. with `org-element-map', and remove
> all :parent references if you don't need them.
I figured out how to follow this advice. I can even make valid JSON
From the filtered parse tree by handing it to Edward O'Conner's
json.el (link in exa
>
> How about the following resolution? We rename ob-sh.el to ob-shell.el.
> New "shell" code blocks could use the value of the
> `org-babel-sh-command' environment variable. Then sh, bash, zsh, csh,
> ash, dash (am I missing any other common ones) use the specific shell
> specified.
>
The attac
Hi,
as I already told, I'm a really newbe (to org-mode, as well as emacs)
I'm starting from the very beginning:
following the Doc (here:
http://orgmode.org/worg/org-tutorials/orgtutorial_dto.html)
I wrote my firs TODO list.
But when I press C-c C-t over a TODO element, it appear DONE, write near
I think this change could make it easier to reproduce problems with
Org-mode loaded and without the user's personal config loaded.
Thoughts?
---
Makefile | 1 +
mk/default.mk | 13 +
2 files changed, 14 insertions(+)
diff --git a/Makefile b/Makefile
index f95bcb2..ce06116 1006
Eric Schulte writes:
> I understand your point, but in reality I doubt there are many systems
> on which people use Org-mode with code blocks and on which sh is
> available but no bash is installed.
You might want to widen your horizon on the "many systems" front a bit.
The typical BSD system has
>>
>> I understand your point, but in reality I doubt there are many systems
>> on which people use Org-mode with code blocks and on which sh is
>> available but no bash is installed.
>
> That may be true on some flavors of Linux, but on BSDs:
>
> bash is not the normal shell (and is not part of
Eric Schulte writes:
> Greg Troxel writes:
>
>> Eric Schulte writes:
>>
Just an fyi: I had to set org-babel-sh-command to "bash" for this to
work. Why is "sh" the default value of this variable?
>>>
>>> I think sh is more portable, but I guess almost any system should have
>>> bash a
Greg Troxel writes:
> Eric Schulte writes:
>
>>> Just an fyi: I had to set org-babel-sh-command to "bash" for this to
>>> work. Why is "sh" the default value of this variable?
>>>
>>
>> I think sh is more portable, but I guess almost any system should have
>> bash as well, I've just changed this
Eric Schulte writes:
>> Just an fyi: I had to set org-babel-sh-command to "bash" for this to
>> work. Why is "sh" the default value of this variable?
>>
>
> I think sh is more portable, but I guess almost any system should have
> bash as well, I've just changed this default to bash.
(Assuming y
Dror Atariah writes:
> Today I realized that I cannot execute successfully 'org-mobile-push'. In
> particular here is the output from '*Messages*':
>
> Creating agendas...
> Agenda written to Org file /Users/drorata/Dropbox/MobileOrg/agendas.org
> Creating agendas...done
> Saving all Org-mode bu
I would use links for this purpose, which org-mode would get right across
lines. For instance, here is a cite link:
https://github.com/jkitchin/jmax/blob/prelude/jorg-bib.el#L332
so you use cite:bibkey1,bibkey2 or [[cite:bibkey1, bibkey2]] instead of
\cite{bibkey1,bibkey2}. At export time, the lin
Hi!
I'm using org-mode with the LaTeX export to write a book. I'm having issues
with inline LaTeX citations (\cite{some label}) and glossary references
(\gls{some label}). When the label (the thing in between the curly braces)
is split across lines, the org-mode LaTeX exporter escapes the curly
br
Hello,
When results caching is enabled, and when the hash must be updated, the
"meta-lines" in front of the results block are _deleted_.
Such meta-lines include:
- ATTR_LaTeX lines
- BEGIN/END_CENTER environments
ECM:
--8<---cut here---start->8---
#+PROPERTY:
James Harkins writes:
> $ git status
> # On branch hjh8.2
You are on your own branch, with unknown modifications.
> In toplevel form:
> ox-texinfo.el:1683:1:Warning: !! The file uses old-style backquotes !!
> This functionality has been obsolete for more than 10 years already
> and will be remov
Today I realized that I cannot execute successfully 'org-mobile-push'. In
particular here is the output from '*Messages*':
Creating agendas...
Agenda written to Org file /Users/drorata/Dropbox/MobileOrg/agendas.org
Creating agendas...done
Saving all Org-mode buffers...
(No files need saving)
Savi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/13/13, 01:26 , Suvayu Ali wrote:
> On Thu, Dec 12, 2013 at 10:00:22AM +0100, Rainer M Krug wrote:
>>
>> On 12/10/13, 21:50 , Samuel Wales wrote:
>>> gitpullv () { #echo \=== maybe need to grab tags head=`git
>>> rev-parse --verify HEAD` echo
42 matches
Mail list logo
