>>> "Uwe" == Uwe Brauer writes:
> Which is what I want. When I convert the org file to latex I am again
> asked to execute the src block, which I don't want since it is already
> executed. How can I avoid this question, without deleting the src block.
> This is important if I have a
I just checked and situation is absurd. Here is the minimal example:
,
|
| #+begin_src matlab :results output latex :exports results
| X=[1];
| disp('\begin{displaymath}')
| fprintf('X&=%g \n', X)
| disp('\end{displaymath}')
| #+end_src
|
| #+RESULTS:
| #+BEGIN_EXPORT latex
| \begin{
Thierry Banel writes:
> Alternatively you have the orgtbl-aggregate package available on Melpa.
>
> #+BEGIN: aggregate :table "myvalues" :cols "min(Values) max(Values)
> mean(Values)"
>
> | min(Values) | max(Values) | mean(Values) |
> |-+-+--|
> | 2 |
Karl Voit writes:
> Leslie helped here by mentioning vmin/vmax which is that obvious
> that I do feel embarrassed now ;-)
>
> #+TBLFM:
> @2$1=vmin(remote(myvalues,@2$1..@>$1))::@2$2=vmax(remote(myvalues,@2$1..@>$1))::@2$3=vmean(remote(myvalues,@2$1..@>$1))::@2$4=remote(myvalues,@2$1)::@2$5=remot
"Raymond Zeitler" writes:
> C-c C-w cannot seem to recognize any of my agenda files, even though
> org-refile-targets is set to (in custom-set-variables):
>
> (org-refile-targets (quote ((org-agenda-files :regexp . "Tasks"
>
> Suppose org-agenda-files contains "~/proj1.org" "~/proj2.org" "~/p
Michaël Cadilhac writes:
> Here's the ECM.
>
> init.el:
> (require 'org)
> (setq org-refile-use-outline-path (quote file))
>
> Now open an Org file, say foo.org, and type C-u C-c C-w foo.org/ RET
> At org.el:11832, pos is nil.
Confirmed here with Org 9.0.5. I think it's from
org-refile-check-po
Hello,
Chris Kauffman writes:
> Apologies for the earlier diff-blast: I did not see the advice on the
> org-mode contributions page that patches generated via
> git format-patch master
> are preferred. Please find four patches attached which now include
> modifications to ORG-NEWS, org.texi,
Hello,
Eric Abrahamsen writes:
> I'm writing an Emacs manual in Org, using
> https://github.com/tarsius/ox-texinfo-plus to make things a bit
> easier.
I don't know that library, but as a biased POV, it would be nice to use
"ox-texinfo" and let us know about its shortcomings. Just saying.
Regar
Hello,
Christian Garbs writes:
> The next iteration of the patch should include ob-vala.el itself, some
> tests and an ORG-NEWS entry.
Great! Thank you.
> Regarding the lexical-binding: How can I check if byte-compiling is
> successful?
M-x emacs-lisp-byte-compile
Regards,
--
Nicolas Goaz
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> I'm writing an Emacs manual in Org, using
>> https://github.com/tarsius/ox-texinfo-plus to make things a bit
>> easier.
>
> I don't know that library, but as a biased POV, it would be nice to use
> "ox-texinfo" and let us know abo
> On Aug 3, 2017, at 1:04 AM, Uwe Brauer wrote:
>
>
>
> I just checked and situation is absurd. Here is the minimal example:
> [snip]
>
> When I set org-export-babel-evaluate nil, then the code is *not*
> evaluated, *but* the code block *and* the result are exported.
>
[snip]
> When I set or
> On Aug 2, 2017, at 4:22 PM, Jeremie Juste wrote:
>
>
>
> Hello
>
>>
>> Putting together a macro seems like the best option. Recall that you
>> can use elisp in macros by placing it between `(eval’ and `)', so the
>> following emits “def’ in all but latex exports and “abc” for latex.
>>
Hi,
I have the following code block in my org mode based literate programming
notes:
#+BEGIN_SRC python
print('1+2 > 4 is ', 1+2 > 4)
print("What is 3 + 2?", 3 + 2)
#+END_SRC
When I tangle it and run the script, it gives me expected output as follows:
> python notes.py
1+2 > 4 is False
What is
Hi,
Is it possible to add custom arguments to source code evaluation in org
babel? For example, if the source code block is:
#+BEGIN_SRC python
# valid comment 1
print("Hi there!") # valid comment 2
print("# Invalid comment! #UsefulForHashtags!")
print ("Space is fine here!")
#+END_SRC
The gener
Shell is using python3 and org-mode python2?
On Aug 3, 2017 8:31 PM, "Dushyant Juneja" wrote:
> Hi,
>
> I have the following code block in my org mode based literate programming
> notes:
>
> #+BEGIN_SRC python
> print('1+2 > 4 is ', 1+2 > 4)
> print("What is 3 + 2?", 3 + 2)
> #+END_SRC
>
> When
Lookup "Org babel results" in Google and you should find the right
section of the manual. You need to set the :results keyword.
I don't mean this in a snide way, but do you keep your config in version
control? e.g. if you have it stored in git, you can bisect it and find
the change that caused the problem.
Other than that, you can probably find the problem using the bug-hunter
package. It can bisect your init file and fi
Hello,
As of today, TODO now appears with three sets of un-requested double
colons after it, as in TODO :: :: ::
The behaviour doesn't occur with emacs -q, so the cause is presumably in
my ~/.emacs. I can't work out what's wrong with my org-todo-sequence,
which is:
(setq org-todo-keywords (quot
Hey Dov,
Bull's eye! Never realized that could hurt.
It so happened that I set the correct python version in my shell before
starting emacs. However, my bashrc file was hardwired to a different
version, which org used every time for evaluating the src blocks.
Thanks for the help!
Dushyant
On Th
"Berry, Charles" writes:
Hello,
Thanks for the update
>>
>
> I think this is obsolete. It fails on org-9.0.9. What version of org are you
> using?
>
> In any case replacing the ~(if ...)~ by ~org-export-current-backend~ will fix
> it.
>
>
> Another case were adding dates to Worg entries mig
>>> "Berry," == Berry, Charles writes:
>> On Aug 3, 2017, at 1:04 AM, Uwe Brauer wrote:
>>
>>
>>
>> I just checked and situation is absurd. Here is the minimal example:
>> [snip]
>>
>> When I set org-export-babel-evaluate nil, then the code is *not*
>> eva
On Wed, Aug 2, 2017, at 11:53 AM, Tyler Smith wrote:
>
> Is it possible to configure org-babel to ignore any customization files,
> such as .emacs.d/init_bash.el and .bashrc?
>
After some digging around, it looks like this isn't possible.
~org-babel~ starts shell sessions via the standard functi
Dear Adam,
> Adam Porter writes:
> I don't mean this in a snide way, but do you keep your config in
> version control? e.g. if you have it stored in git, you can
> bisect it and find the change that caused the problem.
> Other than that, you can probably find the problem usi
Eric Abrahamsen writes:
> Oh I don't think it's about shortcomings, just about having a version
> that's tweaked specifically for writing Emacs manuals. I _really_ want
> my packages to have info manuals, and I _really_ don't want to learn how
> to write texinfo. I saw Rasmus' Org manual in org,
Tyler Smith writes:
> On Wed, Aug 2, 2017, at 11:53 AM, Tyler Smith wrote:
>>
>> Is it possible to configure org-babel to ignore any customization files,
>> such as .emacs.d/init_bash.el and .bashrc?
>>
> After some digging around, it looks like this isn't possible.
> ~org-babel~ starts shell s
Hello,
Thomas von Dein writes:
> currently when exporting a table to CSV, fields are quoted automatically
> if they contain a comma or a quote character. The regexp for this
> determination is hard-coded in 'org-quote-csv-field.
>
> This is good for most use cases. However, if you want to import
Colin Baxter writes:
> Thanks for the suggestion, but I think I may be missing something. My
> emacs init has not changed. My org keyword settings have worked for a
> few years satisfactorily - until that is today. I think I need to bisect
> org-mode to find the case? I've tried reverting a coupl
Nicolas Goaziou writes:
> Eric Abrahamsen writes:
>
>> Oh I don't think it's about shortcomings, just about having a version
>> that's tweaked specifically for writing Emacs manuals. I _really_ want
>> my packages to have info manuals, and I _really_ don't want to learn how
>> to write texinfo.
and from memory, you can also tell excel what the data type of each
column in a csv file is.
Nicolas Goaziou writes:
> Hello,
>
> Thomas von Dein writes:
>
>> currently when exporting a table to CSV, fields are quoted automatically
>> if they contain a comma or a quote character. The regexp for
Eric Abrahamsen writes:
> Nicolas Goaziou writes:
>
>> Eric Abrahamsen writes:
>>
>>> Oh I don't think it's about shortcomings, just about having a version
>>> that's tweaked specifically for writing Emacs manuals. I _really_ want
>>> my packages to have info manuals, and I _really_ don't want
"Raymond Zeitler" writes:
> 1. org-refile-targets ... value is ((org-agenda-files :regexp . "Tasks"))
> Seems OK. But then I see that org-refile-target-verify-function is nil,
> which seems like a problem. Mind you, this is the default configuration,
> and I'm not sure what to change it to.
>
31 matches
Mail list logo
