Nick Dokos gmail.com> writes:
> Yes, you will be happiest when you are assimilated
:borg:
> > Would be nice to have org versions of all info files.
>
> [...] why do you
> want to have org versions of all info files? What would the benefits
> be?
>
> [...] But rewriting
>
Hello,
I have encountered two related misbehaviors in the parser/exporter.
The first manifests if you type the following line into an org-mode
buffer and execute M-: (org-element-context) with point on the ‘f’; the
result is a subscript object, whereas I would have expected an
underline:
'_foo_
On 12/09/2013 02:53 PM, Nick Dokos wrote:
> Catonano writes:
>
>> I' m trying to follow the examples at this page
>>
>> http://orgmode.org/manual/HTML-doctypes.html#HTML-doctypes
>>
>> to transform
>>
>> #+BEGIN_ASIDE
>> Lorem ipsum
>> #+END_ASIDE
>>
>> in
>>
>>
>>Lor
Suvayu Ali gmail.com> writes:
> Firstly, I think the unicode bit is a terrific improvement; specially
> the two options: grid and continuous. I think there are two distinct
> problems here: the plot as shown in org, and export. We should not
> confuse the two.
>
> I will suggest for the moment
Brady Trainor writes:
> Brady Trainor uw.edu> writes:
> ...
> Should probably just get comfortable with the info version of elisp
> manual.
Yes, you will be happiest when you are assimilated :-) Emacs insists on
info files for all packages distributed with it, so info is the lingua
franca.
>
Brady Trainor uw.edu> writes:
>
> [...] I think I'll Pandoc the manual into org to practice the manual's
>
> navigation.
>
>
Converting the html version to org met with some difficulties, such as
carriage returns and pandoc giving an overflow.
Should probably just get comfort
Sebastien Vauban writes:
> Fixed with:
>
> --8<---cut here---start->8---
> ;; accented characters on graphics
> (setq org-babel-R-command
> (concat org-babel-R-command " --encoding=UTF-8")))
> --8<---cut here---end-
Achim Gratz writes:
> Eric Schulte writes:
>> I just pushed up a change which fixes this when exporting on my system,
>> if the problem persists please provide an ECM.
>
> This test is still failing:
>
> Test test-ob/noweb-expansions-in-cache condition:
> (void-variable <>)
>FAILED 149/4
gitpullv () {
#echo \=== maybe need to grab tags
head=`git rev-parse --verify HEAD`
echo
git pull --stat --log | cat
echo
newhead=`git rev-parse --verify HEAD`
if [ "$newhead" != "$head" ]
then
git log --pretty=tformat:%s ORIG_HEAD.. | cat
# git log -
Nick Dokos gmail.com> writes:
>
> Brady Trainor uw.edu> writes:
> > synopsis: want (clickable) customize to open in a new frame
> >
>
> Fiddling with the following variable may help (NB: untested,
> and no time to dig, so I may be leading you up the garden path):
>
> ,
> | or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/13, 20:31 , Nick Dokos wrote:
> Rainer M Krug writes:
>
>> On 12/10/13, 16:59 , Nick Dokos wrote:
>>> ... Be that as it may, you can try something like this hack
>>> (those are backticks around the git pull - it's under the ESC
>>> key in
Rainer M Krug writes:
> On 12/10/13, 16:59 , Nick Dokos wrote:
>> ...
>> Be that as it may, you can try something like this hack (those are
>> backticks around the git pull - it's under the ESC key in the upper
>> left hand corner on most US keyboards but it may be somewhere else
>> on yours):
>>
Eric Schulte writes:
> I just pushed up a change which fixes this when exporting on my system,
> if the problem persists please provide an ECM.
This test is still failing:
Test test-ob/noweb-expansions-in-cache condition:
(void-variable <>)
FAILED 149/491 test-ob/noweb-expansions-in-cach
François Pinard writes:
> Hi, Org people.
>
> Let me make this report from memory, now that I'm back home! :-)
>
> In an Org file, a coworker used "#+BEGIN_SRC shell" where he should have
> written "#+BEGIN_SRC sh". While this looks like a benign error to me,
> it broke my publishing script, and
"Sebastien Vauban" wrote:
> John Hendy wrote:
>> Can you do it straight from R? Might be a better place to start? If not,
>> I'd look into that first to avoid googling org and ESS stuff in vain!
>
> The 1'42" demo on http://screencast.com/t/A9q6CQlLY6 clearly shows that:
>
> - It (now [1]) works fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/13, 18:12 , Achim Gratz wrote:
> Achim Gratz writes:
>> Rainer M Krug writes:
>>> git checkout master make update
>>
>> This doesn't update at all since you never do a "git pull" on
>> master.
>
> Scratch that, I was imagining an "update2"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/10/13, 16:59 , Nick Dokos wrote:
> Rainer M Krug writes:
>
>> Hi
>>
>> I have a question concerning a bash script to update org (and ess
>> in the same way but in a different script).
>>
>> The script I use to update org looks as follow:
>>
"Sebastien Vauban" writes:
> Hello,
>
> After this morning's update [1], I get the following backtrace when executing
> R code.
>
I just pushed up a change which fixes this when exporting on my system,
if the problem persists please provide an ECM.
Thanks for the report!
--
Eric Schulte
http
Achim Gratz writes:
> Rainer M Krug writes:
>> git checkout master
>> make update
>
> This doesn't update at all since you never do a "git pull" on master.
Scratch that, I was imagining an "update2" where you clearly wrote
"update". In any case (and to answer Nick Dokos' remark) make always
does
Hi, Org people.
Let me make this report from memory, now that I'm back home! :-)
In an Org file, a coworker used "#+BEGIN_SRC shell" where he should have
written "#+BEGIN_SRC sh". While this looks like a benign error to me,
it broke my publishing script, and I did not figure at once what was
hap
Rainer M Krug writes:
> git checkout master
> make update
This doesn't update at all since you never do a "git pull" on master.
> which works nicely, but I would like to only execute the "make update"
> if git updated something - I am sure this is possible, but how?
I really don't see why you'd
Rainer M Krug writes:
> Hi
>
> I have a question concerning a bash script to update org (and ess in
> the same way but in a different script).
>
> The script I use to update org looks as follow:
>
> #!/bin/sh
> cd ~/.emacs.d/org-git
>
>
> #!/bin/sh
> git checkout master
> make update
>
Brady Trainor writes:
> synopsis: want (clickable) customize to open in a new frame
>
Fiddling with the following variable may help (NB: untested,
and no time to dig, so I may be leading you up the garden path):
,
| org-link-frame-setup is a variable defined in `org.el'.
| Its value is ((
Hello everyone,
Assume I have an org-mode file that contains the following:
--
#+OPTIONS: tex:imagemagick
#+LaTeX_HEADER: \usepackage[siunitx]{circuitikz}
* Test circuit
#+begin_lateX
\begin{circuitikz}[scale = 1.0] \draw
(0,0) node[anchor=east]{$V_{in} -$}
Hi Nicolas,
Nicolas Girard writes:
> unless i'm misunderstood, the preferred Url to the Org Mode ELPA
> server is "http://orgmode.org/elpa/";, which replaced
> "http://orgmode.org/pkg/daily/";.
Indeed. I deleted the http://orgmode.org/pkg/ directory.
--
Bastien
Miguel Ruiz writes:
[...]
> #+begin_src calc :var x=0.8
> sqrt(x)
> #+end_src
I confirm that this doesn't work. However, putting 0.8 in quotes, as in
var="0.8", works for me.
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.2.4-322-gece429
Detlef Steuer writes:
> Hi!
>
> I spent most of yesterday afternoon on toying with org-caldav.
[...]
> The third (large) file gives a lot of problems.
>
> 1. I had the same error message as Daniel. I remember my critical UID
>beginning with TS10, too. Strange.
Detlef & Daniel,
I reme
Hi,
the problem is that calc does not operate on regular elisp types but instead
uses a different format: (float NUM EXP) for decimal floats. But ob-calc.el
seems to simply push any value it gets on the stack and assigns it to a
variable. And since calc treats anything which isn't in such a l
Hi folks,
unless i'm misunderstood, the preferred Url to the Org Mode ELPA
server is "http://orgmode.org/elpa/";, which replaced
"http://orgmode.org/pkg/daily/";.
Apparently there is still a reference to the outdated url on the very
page "http://orgmode.org/pkg/daily/";, which is confusing (at le
Hi,
Please, I am communicating the following problematic behaviour:
#--- problematic code
#+begin_src calc
sqrt(0.8)
#+end_src
#+RESULTS:
: 0.894427191 # OK
#+begin_src calc :var x=0.8
sqrt(x)
#+end_src
#+RESULTS:
=Debugger entered--Lisp error: (wrong
Hi!
I spent most of yesterday afternoon on toying with org-caldav.
It came out as a more or less frustrating afternoon.
A while (a year?) ago I had setup a _working_ script to export multiple
calendars to owncloud. Owncloud wasn´t stable enough at that time, so I
stopped using it. Now I´m trying
Hello,
After this morning's update [1], I get the following backtrace when executing R
code.
--8<---cut here---start->8---
Debugger entered--Lisp error: (void-variable params)
(org-babel-merge-params (nth 2 info) params)
(sort (org-babel-merge-params (nth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/09/13, 22:36 , David Rogoff wrote:
> Sorry if this has been discussed but I wasn’t able to find info on
> it. I have lots of source blocks in my org files (tcl, verilog,
> shell-script, etc). I want to be able to highlight (e.g. *bold*)
> t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
I have a question concerning a bash script to update org (and ess in
the same way but in a different script).
The script I use to update org looks as follow:
#!/bin/sh
cd ~/.emacs.d/org-git
#!/bin/sh
git checkout master
make update
wh
34 matches
Mail list logo
