Running org-map-entries on an org file with tags results in an infinite
loop.
Example function using org-map-entries:
(defun scrum-test ()
(interactive)
(org-map-entries '(lambda () (message "%s" (org-entry-properties
(point) 'standard
(message "done"))
Example org
The Free Software Foundation has changed the GNU Mailman settings on
this list. The short version is that any subject prefix or message
footer has been removed, allowing us to turn off DMARC from munging.
Any list administrator for this list is free to change these settings
back, instructions are
I'm trying to capture the output of rg but I'm getting no output (I'm getting
the message "Code block produced no output" in the minibuffer.
I've also tried ag and pt which don't work either. It works with grep but this
is too slow for my use-case.
Example:
#+BEGIN_SRC shell
mkdir -p
Hi,
> One issue for me is the positioning of the level 0 property drawer.
> Having the requirement for that drawer starting in the very first
> line is too strong for me. I guess one would at least like to have
> the option to add some configuration with the ‘-*-...-*-’ construct
> which
Hey!
It would be great if repeating dates supported business days. So you could
have repeating date <2019-01-01 Mon +1b>. Is this request being worked on /
do you think it is worth implementing?
Thanks, Harry
Hi,
It seems that org-mode does not correctly parse custom to-do states when
they are preceded by a priority. This example org-mode file demonstrates
the issue:
#+TODO: TODO BLOCKED DONE
* TODO [#A] this works
* BLOCKED [#A] this works
* [#A] TODO this works
* [#A] BLOCKED
Hello, everyone.
I recently updated to org 9.2 from org-melpa, and I have the following issue:
I use org with org-babel to write a book with many examples and illustrations.
I use ob-plantuml and ob-scheme in particular.
The problem is that for ob-plantuml I need the value of point be right
On Tuesday, 29 Oct 2019 at 15:57, Vladimir Nikishkin wrote:
> The problem is that for ob-plantuml I need the value of point be right
> after the :file header parameter, because plantuml always requires a
> file name.
I don't see this in my configuration. But it could be that I do not
understand
I used org 8 until recently, and it used to be that I could type "<"
at the beginning of a line, and it would be still a single "<" (thus
allowing the expansion of structured templates with TAB)
In org 9.2 electric-pair-mode seems to be working all the time.
What is the recommended way of making
On Tuesday, 29 Oct 2019 at 16:09, Vladimir Nikishkin wrote:
> I used org 8 until recently, and it used to be that I could type "<"
> at the beginning of a line, and it would be still a single "<" (thus
> allowing the expansion of structured templates with TAB)
Expansion of structured templates is
In the version 8 of org-mode you could indicate where to put the point
after the template is expanded. In the template
(list "p" "#begin_src plantuml :file ? :export both \n#end_src"),
after the template is expanded, the point would be located after
:file, whereas in the template (list "SO"
agzam.ibragi...@gmail.com writes:
> While fooling around with capture templates, I have also noticed this:
>
> (progn
> (setq org-popup-calendar-for-date-prompt t)
> (read-date t)))
>
> When prompted, if you type something like "13:00" - it returns correct,
> expected datetime.
>
> But, if
No it is not, please, don't disinform people.
вт, 29 окт. 2019 г. в 17:03, Fraga, Eric :
>
> On Tuesday, 29 Oct 2019 at 16:50, Vladimir Nikishkin wrote:
> > I think, these are two different mechanisms. C-c C-, works as expected.
> > The "<" mechanism comes from org-tempo, and is faster, because
On Tuesday, 29 Oct 2019 at 17:06, Vladimir Nikishkin wrote:
> No it is not, please, don't disinform people.
Not intending to do so but please clarify: in which way am I
misinforming people?
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-544-gd215c3
On Tuesday, 29 Oct 2019 at 16:50, Vladimir Nikishkin wrote:
> I think, these are two different mechanisms. C-c C-, works as expected.
> The "<" mechanism comes from org-tempo, and is faster, because you
> don't have to choose anything.
I don't know anything about org-tempo but, just to be clear,
ian martins writes:
> Hello, I wrote some helper functions for generating a scrum board and
> reports that is built on top of org-mode. The project is currently
> emacs-scrum. I submitted it to melpa recently and got the suggestion
> to name the package org-scrum since it's based on org-mode. Is
And this question is _not_ about the template expansion, but about the
electric-pair-mode.
вт, 29 окт. 2019 г. в 17:06, Vladimir Nikishkin :
>
> No it is not, please, don't disinform people.
>
> вт, 29 окт. 2019 г. в 17:03, Fraga, Eric :
> >
> > On Tuesday, 29 Oct 2019 at 16:50, Vladimir
I think, these are two different mechanisms. C-c C-, works as expected.
The "<" mechanism comes from org-tempo, and is faster, because you
don't have to choose anything.
вт, 29 окт. 2019 г. в 16:21, Fraga, Eric :
>
> On Tuesday, 29 Oct 2019 at 16:09, Vladimir Nikishkin wrote:
> > I used org 8
Please, consider visitiong M-x info-display-manual RET org RET section
15.2, paragraph 4.
вт, 29 окт. 2019 г. в 18:08, Fraga, Eric :
>
> On Tuesday, 29 Oct 2019 at 17:06, Vladimir Nikishkin wrote:
> > No it is not, please, don't disinform people.
>
> Not intending to do so but please clarify: in
Am 29.10.19 um 16:08 schrieb Julius Müller:
> Am 29.10.19 um 15:57 schrieb Vladimir Nikishkin:
>> Please, consider visitiong M-x info-display-manual RET org RET section
>> 15.2, paragraph 4.
>
> Well, there's at least something missing in that documentation. Without
> any config file active, but
> On Tue, 29 Oct 2019 15:14:37 +0100, Thibault Polge said:
Thibault> Robert Pluim writes:
>> end of line *is* a whitespace character, but Iʼm not going to argue
>> that. Iʼm going to argue that this doesnʼt cover the case of a '#' at
>> EOB without a newline, hence saying
I'm not sure how this feature is called, but in Org you can restrict a line
to a given exporter by prepending it with, eg, #+latex:
There's a bug with some exporters f treat these lines as paragraph breaks,
some don't. For example, the following input:
Hello
#+latex: \TeX{}
World
#+html: Wide
> On Mon, 28 Oct 2019 17:16:55 +0100, Nicolas Goaziou
> said:
Nicolas> Hello,
Nicolas> Thibault Polge writes:
>> Thanks Nicolas, just a small detail though: unless this is a planned
>> (breaking) change, I believe the description you linked should read:
>>
>>
Robert Pluim writes:
> end of line *is* a whitespace character, but Iʼm not going to argue
> that. Iʼm going to argue that this doesnʼt cover the case of a '#' at
> EOB without a newline, hence saying 'zero or more' would be better.
But zero-or-more would mean that this line:
#Alpha
Is a
> Closing the loop. I can confirm that my example works on this commit
> (one before the relevant change) (thanks, Chuck!).
>
> commit ed9bdfd220b75233e5bae2ef39164d14624060fa (HEAD)
> Merge: 0954d4c25 0ae2e656d
> Author: Marco Wahl
> Date: Fri Oct 5 00:54:19 2018 +0200
>
> Completely stumped
On Mon, Oct 28, 2019 at 12:46 PM Jack Kamm wrote:
>
> > 2) why does this [still] work for Jack? (Jack, what's M-x org-version for
> > you?)
>
> I tested on my laptop and desktop, both work for me, they are running the
> following 2 versions of org:
>
> Org mode version 9.2.4
Am 29.10.19 um 15:57 schrieb Vladimir Nikishkin:
> Please, consider visitiong M-x info-display-manual RET org RET section
> 15.2, paragraph 4.
Well, there's at least something missing in that documentation. Without
any config file active, but with org mode loaded, those abbreviations
are not
On Tue, Oct 29, 2019 at 9:51 AM Jack Kamm wrote:
>
> > Closing the loop. I can confirm that my example works on this commit
> > (one before the relevant change) (thanks, Chuck!).
> >
> > commit ed9bdfd220b75233e5bae2ef39164d14624060fa (HEAD)
> > Merge: 0954d4c25 0ae2e656d
> > Author: Marco Wahl
Thibault,
in case you might find this useful, you can use the @@ construct to put
things inline, causing less issues with paragraphs. For instance, you
can write @@latex:\TeX{}@@.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-544-gd215c3
> I doubt it. There are 3 paragraphs, even for LaTeX, since there are
> empty lines.
I believe there may have been a communication issue somewhere, since you
cite my message with extra \n --- there are no empty lines in my
original message. For reference, here's the exact input I've used:
I wrote about a potential solution to this issue at
https://emacs.stackexchange.com/questions/50216/org-mode-code-block-parentheses-mismatch/52209#52209
.
You might find a solution that works for you there.
John
---
Professor John Kitchin
Doherty Hall A207F
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
On Tuesday, 29 Oct 2019 at 23:50, Vladimir Nikishkin wrote:
> The MWE would be the following:
>
> #+begin_src scheme
> (display (< 1 3))
> #+end_src
>
> In this example, if you put the point on the "<" symbol, it is
> highlighted (fontified) together with the ")" following 3, which is
> incorrect,
`org-tempo' is the replacement. It is mentioned in the docstring for
`org-structure-template-alist'.
Here is what I have in my `emacs-init.org' file:
(The letter `p' denotes where point should land. `n' is a newline. See the
docstring for `tempo-define-template' for more details.)
Hello,
Thibault Polge writes:
> I'm not sure how this feature is called, but in Org you can restrict a line
> to a given exporter by prepending it with, eg, #+latex:
>
> There's a bug with some exporters f treat these lines as paragraph breaks,
> some don't. For example, the following input:
On Tuesday, 29 Oct 2019 at 22:57, Vladimir Nikishkin wrote:
> Please, consider visitiong M-x info-display-manual RET org RET section
> 15.2, paragraph 4.
You must have a different version of the manual than I have. For me,
this section is on header arguments for working with source code and the
Thibault Polge writes:
> As you can see, the LaTeX PDFs have everything in a single line, the
> HTML output displays four separate paragraphs.
This is because the definition of a paragraph in HTML, or LaTeX,isn't
the same as in Org. In this particular case, HTML matches Org
definition. LaTeX is
That's probably a working solution, but I still wonder why org 8
doesn't have this problem.
Thanks anyway.
ср, 30 окт. 2019 г. в 00:40, Fraga, Eric :
>
> On Tuesday, 29 Oct 2019 at 23:50, Vladimir Nikishkin wrote:
> > The MWE would be the following:
> >
> > #+begin_src scheme
> > (display (< 1
What is the canonical difference between org-insert-structure-template
and org-tempo then?
I think, emacs skeleton libraries (M-x info-display-manual RET
autotype RET) support placing the point (with a "_" marker)
ср, 30 окт. 2019 г. в 00:43, Berry, Charles :
>
> `org-tempo' is the replacement.
"Fraga, Eric" writes:
> On Tuesday, 29 Oct 2019 at 16:50, Vladimir Nikishkin wrote:
>> I think, these are two different mechanisms. C-c C-, works as expected.
>> The "<" mechanism comes from org-tempo, and is faster, because you
>> don't have to choose anything.
>
> I don't know anything about
>> https://ivanaf.com/Automatic_Latex_Fragment_Toggling_in_org-mode.html
Exactly what I wanted. I will be using this.
BTW just as a minor point, no need for setq when byte-compiling,
https://www.gnu.org/software/emacs/manual/html_node/elisp/Compilation-Functions.html#Compilation-Functions
/This
Cool, I didn't know about maxima. I will look into trying it out. Thanks!
Regards,
Dmitrii
пн, 28 окт. 2019 г. в 07:08, briangpowell . :
> * Suggest reviewing these free software packages:
> https://itsfoss.com/latex-editors-linux/
>
> ** LyX and/or Kile are my faves
>
> ** Suggest trying these
On Tuesday, 29 Oct 2019 at 16:17, Nick Dokos wrote:
> Not quite: there is still an emulation of the old mechanism if you
>
> (require 'org-tempo)
Ah, thanks for clarifying.
--
Eric S Fraga via Emacs 27.0.50, Org release_9.2.6-552-g8c5a78
43 matches
Mail list logo
