Having re-read Vladimir's original question, it looks like I may have
misunderstood it at first. Now I'm wondering: What's the use case for
referencing a code block but commenting out the first line?
On Tue, 25 Feb 2020 at 09:00, Johannes Dahl wrote:
>
> Hi,
>
> That's a fun coincidence, I ran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Samuel Wales writes:
> no opinion on anything but a suggestion.
>
> i really like these little scripts that update your org files so they
> are compatible with new org versions.
>
> perhaps one can give them an argument or something to work on
Hi,
That's a fun coincidence, I ran into this behaviour a couple of days
ago as well. For anyone wondering why one would want to comment out
their noweb tags but still expect them to result in uncommented code
expansion: if one is to edit a source block containing Noweb tags, the
emacs mode for
Hello, there
I bumped into a problem running src blocks using a remote (tramp) :dir. I've
looked into it and found that the problem is that a temporary file is passed
as a remote path to the remote process (temp file should be local to remote
process).
I'm attaching fixes for python and shell
Let's say I have a standard org file I want to have created multiple times.
I've created a template file and told Emacs autoinsert where it is. Here's
the relevant in my init
(use-package autoinsert
:ensure t
...
:config
(define-auto-insert "poolchem.org?$" "poolchem.org"))
So in this
I don't know if this is useful. But this is what I could come up with. This
might at least motivate somebody to think of other possible advantages/uses of
building org-mode capabilities to interact with databases.
Vikas
---
Feature request: To build tools to facilitate using org-mode as a
Hello, everyone
I have the following case:
#+name: test1
#+begin_src shell
LINE to comment
LINE to not comment
#+end_src
#+begin_src shell
#<>
#+end_src
When I expand it, I get:
#LINE to comment
#LINE to not comment
That's not entirely what I want. Can this behaviour be switched off
Hello, everyone
The MWE would be the following:
#+name: empty
#+begin_quote
1
#+end_quote
#+begin_src shell :shebang "#! /usr/bin/chibi-scheme :stdin empty
(/ 1 0)
#+end_src
Now the chibi-scheme shebang is just an example of an app writing
things to stderr. The actual content of the <> doesn't
The MWE would be the following:
#+name: empty
#+begin_quote
#+end_quote
#+begin_src shell :stdin empty
#+end_src
Now if you try to execute the second block, you will get a lisp error.
"Wrong argument integer-or-marker-p"
Remember to cover the basics, that is, what you expected to happen and
no opinion on anything but a suggestion.
i really like these little scripts that update your org files so they
are compatible with new org versions.
perhaps one can give them an argument or something to work on all
agenda files, or a list of files, or somethign liek that?
On 2/24/20, Bastien
Hi,
I use Org mode & agenda on both my personal and work machines, in a
private git repo repository. I use auto-commit and push automatically
from each machine. It works alright. New items go in inbox.org, and I
refile most to tasks.org, which has a structure a little like this:
* Home :@home:
Hi Nicolas,
it seems that org-store-link stored links to headlines as
[[*TODO headline][headline]]
keeping the TODO keyword, if any.
This is fixed in master but I won't if we should document this bug
fix in ORG-NEWS (or if org-store-link was just momentarily broken.)
If org-store-link was
Hi Stardiviner,
stardiviner writes:
>> IMHO we may have several file links such as yours broken: Nicolas,
>> do you think the bugfix should be advertized in ORG-NEWS, along with
>> a helper function to fix file links (ie remove the TODO keyword and
>> priority cookies)?
>
> This broken update
Hi Karl,
Karl Voit writes:
> Retrying when error re-appears.
OK, thanks for the feedback!
--
Bastien
On Mon, Feb 24, 2020 at 10:51 AM Nicolas Goaziou
wrote:
> > Does anyone know why Org is parsing files in random folders when
> > I have a bad ID and a <>?
>
> I don't. You may want to check `org-id-files', or walk the hash table
> `org-id-locations'.
>
(apropos "org-id-files") returns nil,
Hello,
Ken Mankoff writes:
> I thought named IDs were supposed to go into CUSTOM_ID properties
> rather than ID properties. Is this incorrect?
ID are meant to be automatically generated, and stored in a database.
They can work across documents. CUSTOM_ID, OTOH are use-defined values,
internal
Hi Org List,
This is cross-posted here:
https://www.reddit.com/r/emacs/comments/f8t50q/help_debugging_org_os_interaction/
I've run into a strange bug. This is reproducible on my machine with "emacs
-Q", but not with with emacs-sandbox
https://github.com/alphapapa/emacs-sandbox.sh/ so I don't
Bastien writes:
> Hi Eric,
>
> Eric Abrahamsen writes:
>
>> The key is having `org-agenda-sticky' set to t -- this means that we'll
>> let-bind buffer-local variables in a buffer where they're already
>> set.
>
> thanks for the reproducible example, I was able to get the warning.
>
> You can
On Monday, 24 Feb 2020 at 08:18, Jack Kamm wrote:
> This sounds interesting. Do you know of any documentation or examples
> for :prologue and :epilogue? I checked the Worg page for ob-maxima, but
> it didn't mention these header arguments.
I don't know of any documentation. They basically simply
On Monday, 24 Feb 2020 at 08:17, Jack Kamm wrote:
> 1. noweb (as Eric mentioned). Then you only need to write the code
> once, but note that it will be executed twice.
Doesn't need to execute twice: maybe add ":eval no" to the first block,
the one that will be included in the other one?
--
:
Hi Eric,
"Fraga, Eric" writes:
> Longer term, better would be an implementation of :prologue and
> :epilogue options for python src blocks like we have for Maxima. It
> would probably make sense to provide these options for most if not all
> src blocks?
This sounds interesting. Do you know of
Hi RC,
R C writes:
> My python src blocks often have both graphical output as well as the
> results of some numerical calculation displayed using print statements.
>
> When exported I would like the line: return 'img/ex1.png' not to be
> included in the listing of the src block.
>
> Also, the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bastien writes:
> Hi Stardiviner,
>
> stardiviner writes:
>
>> So I did a git bisect. Found this bad commit caused this problem
>> "afd3b04ec * bad ol: Extend open tooling in link parameters".
>
> This will work:
>
> #+begin_src org
>
Hi Bastien,
* Bastien wrote:
>
> Karl Voit writes:
>
>> Easy: I could not find any change of the defaults in my
>> configuration[1]. So all of them have to be the default values.
>>
>> [1] https://github.com/novoid/dot-emacs/blob/master/config.org
>
> I would try setting
On Monday, 24 Feb 2020 at 02:13, R C wrote:
> When exported I would like the line: return 'img/ex1.png' not to be
> included in the listing of the src block.
I don't think this is currently possible in the sense you want.
You could use :noweb where you have one src block referring to others
and
I think you can do something like this. I don't have impala-shell, so
I wasn't able to test this. It worked using another executable though.
This is pretty bare bones, no sessions, etc.
(require 'org)
(require 'ob)
(defun org-babel-execute:impala (body params)
(let* ((code
Hi Stardiviner,
stardiviner writes:
> So I did a git bisect. Found this bad commit caused this problem
> "afd3b04ec * bad ol: Extend open tooling in link parameters".
This will work:
#+begin_src org
[[file:~/Org/Tasks/Computer Todos.org::*厉害的人是怎么分析问题的？][厉害的人是怎么分析问题的？]]
#+end_src
Hi Jack,
Thanks for your response. Sorry for not being clearer.
My python src blocks often have both graphical output as well as the
results of some numerical calculation displayed using print statements.
#+begin_src python :results file
import numpy as np
import matplotlib.pyplot as plt
def
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bastien writes:
> Hi Stardiviner,
>
> stardiviner writes:
>
>> When I open a link like this:
>
> Thanks for testing links, the master branch contains a few changes.
>
>> #+begin_src org
>> [[file:~/Org/Tasks/Computer Todos.org::*TODO
Hi Matt,
Matt Huszagh writes:
> Thanks for the feedback. I've filled out the form you sent and sent it
> to the email listed.
this is now in master, thanks.
--
Bastien
Hi Eric,
Eric Abrahamsen writes:
> The key is having `org-agenda-sticky' set to t -- this means that we'll
> let-bind buffer-local variables in a buffer where they're already
> set.
thanks for the reproducible example, I was able to get the warning.
You can safely ignore it: when redoing
Hi Karl,
Karl Voit writes:
> Easy: I could not find any change of the defaults in my
> configuration[1]. So all of them have to be the default values.
>
> [1] https://github.com/novoid/dot-emacs/blob/master/config.org
I would try setting `org-agenda-before-write-hook' to nil (it is set
to
Hi Stardiviner,
stardiviner writes:
> When I open a link like this:
Thanks for testing links, the master branch contains a few changes.
> #+begin_src org
> [[file:~/Org/Tasks/Computer Todos.org::*TODO 厉害的人是怎么分析问题的？][厉害的人是怎么分析问题的？]]
> #+end_src
>
> I =[M-x toggle-debug-on-error]= got following
Hi Vikas,
Vikas Rawal writes:
> I am essentially thinking of org-mode providing an
> interface for feeding data to recutils.
Yes, that would probably be useful.
If you want to write a feature request, please write it as if the
reader does not know recutils and you precise use-case, so that we
34 matches
Mail list logo
