Kyle Meyer writes:
> Raoul Comninos writes:
>
>> Kyle Meyer writes:
>>
>>> Hmm, isn't this just following the built-in completing-read's behavior?
>>>
>>> (completing-read
>>>"Prompt: "
>>>(list "Chris Bell"
>>> "Phone Chris Bell"
>>> "Meeting with Chris Bell"))
>>>
>
Rodrigo,
i guess part of the answer depends on why you are naming your code
blocks. for me, the main reason is for <>. another is so that
when org-mode asks me if it should run a block, it has a name to tell me
to help in my decision-making.
for <>, there is noweb-ref header argument (see manua
Raoul Comninos writes:
> Kyle Meyer writes:
>
>> Hmm, isn't this just following the built-in completing-read's behavior?
>>
>> (completing-read
>>"Prompt: "
>>(list "Chris Bell"
>> "Phone Chris Bell"
>> "Meeting with Chris Bell"))
>>
>> ;; `C` => Chris Bell -> `` =>
John Kitchin writes:
> Here is one way to do it. You use a :var to "run" the other block.
Thank you very much for the suggestion. It indeed works but I think that
I don't need what I was requesting now that I've found out about the
=:post= header argument.e
After reading your answer, I remem
I'm trying write a test for a recently merged patch[1].
The patch adds the ability for users to specify a function to collect
args to be passed to a custom bulk function.
I'm trying to mock the argument collecting function and the custom bulk
function and then test that the arguments returned fro
Christine Köhn writes:
> Hi,
>
> I always used the manual online as one html page but it does not seem to
> be available since (?) the website revamp. I prefer the manual as one
> page for many reasons. Is it still available online?
>
I've always used the one-page per section version on the web
Here is one way to do it. You use a :var to "run" the other block.
#+NAME: create-file
#+begin_src bash :results silent
cat << EOF > main.txt
foo
bar
EOF
#+end_src
#+BEGIN_SRC python :var run=create-file
with open('main.txt') as f:
print(f.read())
#+END_SRC
#+RESULTS:
: foo
: bar
:
John
-
Is it possible to associate a code block (A) to another code block (B)
so that when (A) is executed (B) is executed beforehand? I'm asking this
because I have a bash code block (B) that creates a file that is then
processed by a python code block (A) so before executing (A) block, the
file needs
I think this question is aimed to people which have Org Mode files
with a lot of source code blocks and those code blocks are usually
assigned a name.
I am asking this question because I just noticed that it is not
possible to have multiple source code blocks with the same name. If
that occurs,
At a first glance, this task seems to be easy:
1. Go to the top of the source code block
2. Insert "#+NAME: <>" or replace the current name.
3. Done.
However, there are multiple scenarios. The attached file =main.org=
contains the possible scenarios that the function must cover in order to
be co
Timothy writes:
#+begin_src diff
org-priority-regexp
- (defvar org-priority-regexp ".*?\\(\\[#\\([A-Z0-9]+\\)\\] ?\\)"
+ (defvar org-priority-regexp "^\\*+.*\\(\\[#\\([A-Z0-9]+\\)\\] ?\\)"
#+end_src
Since this thread seems to suggest it's (1) faster (2) more correct.
If anyone's considering wri
> Ihor Radchenko writes:
> Colin Baxter writes:
>> Odd. The problem has gone away and all is now well. I am tracking
>> the master branch of emacs-28; however, I thought I had checked
>> and got the same error using emacs-27.1.
> This is because .elc files are in .gitign
On 2021-02-14 12:12, John Kitchin writes:
> If it is possible to set up what you want in an entry in
> org-agenda-custom-commands, then you can call it in a program like
>
> #+BEGIN_SRC emacs-lisp
> (org-agenda nil "w" nil)
> #+END_SRC
This is what I ended up doing.
- set up an agenda view with
Hi,
If a line in a paragraph starts with a digit (or letter) + period +
space, Org misinterprets that as a list item. I almost always notice
this only when I export my document, which is a nuisance.
I wonder if there is any standard solution to that, or if I'm missing
something... All that occurr
On 13/02/2021 11:38, Kyle Meyer wrote:
All right, here's
a format-spec-inspired fix. At the very least it needs doc updates and
a comment or two.
Thank you. I am hardly familiar with elisp so it would be difficult for
me to express the same. My comments are mostly a matter of taste.
Sorry,
Colin Baxter writes:
> Odd. The problem has gone away and all is now well. I am tracking the
> master branch of emacs-28; however, I thought I had checked and got the
> same error using emacs-27.1.
This is because .elc files are in .gitignore. Checking out other branch
would leave all the compil
> Robert Pluim writes:
> On Mon, 15 Feb 2021 13:38:42 +, Colin Baxter said:
Colin> This has worked until today. Now if data.org.gpg is opened I
Colin> get an error.
Colin> Debugger entered--Lisp error: (void-variable minor-modes)
Colin> (sensitive-mode t)
> My c
Colin Baxter writes:
> Debugger entered--Lisp error: (void-variable minor-modes)
This looks like master Emacs issue. Did you happen to update Emacs to
master as well? There was a recent commit related to minor-modes
variable. You can search for "0bd846c 1/2: Rename minor-modes to
local-minor-mod
> Thanks again for the nice addition.
My pleasure, thanks for all of your feedback.
Also I took another look at adding a test around this, will hopefully
have another patch to submit for that.
Kevin
> On Mon, 15 Feb 2021 13:38:42 +, Colin Baxter said:
Colin> This has worked until today. Now if data.org.gpg is opened I get an
Colin> error.
Colin> Debugger entered--Lisp error: (void-variable minor-modes)
Colin> (sensitive-mode t)
My crystal ball says youʼre tracking
Hello,
I have an encryption problem that has materialised only today. I
think it's an org-mode issue since that package is the only one I have
refreshed with a new 'pull' today
I have a symmetrically encrypted file data.org.gpg for which I have the
line:
# Local Variables:
# eval: (sensitive-mod
On 2021-02-14 12:12, John Kitchin writes:
> If it is possible to set up what you want in an entry in
> org-agenda-custom-commands, then you can call it in a program like
>
> #+BEGIN_SRC emacs-lisp
> (org-agenda nil "w" nil)
> #+END_SRC
>
> In that snippet, I have the key in an org-agenda-custom-c
Hi Ihor,
No, I am not using undo-tree.
Thanks,
Dmitry
On Mon, Feb 15, 2021 at 1:41 PM Ihor Radchenko wrote:
> Dmitry Knyaginin writes:
>
> > By the way, I have started to test my theory that the bug has to do with
> > the file size, but so far I have not been able to reproduce the bug.
>
> A
On Monday, 15 Feb 2021 at 13:21, Dmitry Knyaginin wrote:
> the beginning, and to be honest I am unsure I understand "not intended for
> that mode". I mean, if I visit plain text files, I guess it does not matter
> which mode I invoke, right?
There are some modes that expect buffers to have specifi
Dmitry Knyaginin writes:
> By the way, I have started to test my theory that the bug has to do with
> the file size, but so far I have not been able to reproduce the bug.
Another guess about your case: I have experienced deleted parts of
buffer and lost history when using undo-tree. Do you happe
On Monday, 15 February 2021 04:39:12 CET you wrote:
> Tim Van den Langenbergh writes:
> > Hello,
> >
> > I've quickly thrown together Babel bindings for Raku[1][2].
> >
> > Unfortunately the raku-mode package does not have its copyright assigned
> > to
> > the FSF, and I'm using the comint mode fro
>
> if you invoke a special mode while visting a file not intended for that
> mode
sound interesting to test... in my case the file has been in org mode from
the beginning, and to be honest I am unsure I understand "not intended for
that mode". I mean, if I visit plain text files, I guess it does
On Sunday, 14 Feb 2021 at 20:45, Timothy wrote:
> By patch "patch" I really mean just someone with commit access doing
> something like:
Hi Timothy,
Sure but the best way is if you prepare a patch with a commit message
that describes the change and post it here. Instructions on Worg on how
to pr
On Friday, 12 Feb 2021 at 11:29, Dmitry Knyaginin wrote:
> I have some wild theories, including a gamma particle hitting my laptop ;)
Something I saw on the emacs developer list: if you invoke a special
mode while visting a file not intended for that mode, it is possible for
contents to be deleted
29 matches
Mail list logo
