Ihor Radchenko writes:
> I think I addressed the raised issues.
> Just merged org-fold upstream.
> Kévin Le Gouguec writes:
>
>> My recipe (based on commit f9dd109bc, Emacs 29.0.50 commit 864c8013fd):
>>
>> $ git switch feature/org-fold-universal-core-tidy
>> $ make autoloads
>> $ emacs -Q
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>>> But it does not help, org-set-property sets always a new property at the
>>> end of the property list.
>>
>>> Any idea what to do (besides touching the function itself)
>>
>>
>> It seems that the culprit is the function
>>
Starting with `emacs -Q', I create a simple file with the following
contents:
--8<---cut here---start->8---
* Clocktable
#+BEGIN: clocktable :maxlevel 3 :emphasize nil :scope file
#+END: clocktable
--8<---cut
On 4/26/22 03:14, Ihor Radchenko wrote:
It is to be expected.
Dynamic block syntax is the following (see manual):
#+BEGIN: dynamic_block_name [args]
...
#+END:
You should not put dynamic block name after #+END:
Thanks! I cut-and-pasted out of the documentation, so it is a doc bug instead:
Russell Adams writes:
> --
> * Fails w/o DOW, end time at 2100 not 0200
>
> <2022-04-28 21:00>--<2022-04-29 02:00>
Confirmed.
The problem is that org-ts-regexp1 does not match "2022-04-29 02:00". I
am not sure why. org-ts-regexp1 looks like it
Max Nikulin writes:
>> This whole timezone staff is complex. I got lost in the emacs devel
>> discussion half-way through. From point of view of API, I would prefer a
>> single function with docstring explaining the necessary caveats.
>
> To have namely a single function that accepts both a list
Nick Dokos writes:
> --8<---cut here---start->8---
> * Clocktable
>
> #+BEGIN: clocktable :maxlevel 3 :emphasize nil :scope file
> #+END: clocktable
> --8<---cut here---end--->8---
>
> I position the cursor on the #+BEGIN
The syntax is:
#+BEGIN: clocktable ...
#+END:
There is no `clocktable' after `#+END:'.
---
doc/org-manual.org | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index af54dc4e87f9..6768ca98dd7f 100644
---
Ignacio Casso writes:
> Actually, I have investigated a little bit and I think the issue is more
> simple
> than that:
>
> - Link abbreviations rely in the variables `org-link-abbrev-alist' for
> global abbreviations and `org-link-abbrev-alist-local' for
> abbreviations defined with #+LINK
Ihor Radchenko writes:
> Ignacio Casso writes:
>
>> So a simple solution to this would be preserving the value of
>> `org-link-abbrev-alist-local' when switching to the temporal buffer. I
>> think this is orthogonal to the issue of the parser, and it's a bug on
>> its own, since as a user I
Abilash S writes:
> I m working with an org file where I create a java source block and
> every time I use a snippet I am receiving the following warning and along
> with it the pointer where the cursor should start auto-fills a tab.
> But the default behaviour is for the cursor to be present in
Hello Everyone,
Is there a way to automatically use the text content of the current
Heading as the EXPORT_FILE_NAME? AFAICT there isn't.
I tend to do most of my Org writing in a few 'mono files' (like todo.org or
wiki.org). I then set my export options to default to subtree and visible
contents
>> (cond ((org-in-regexp org-link-any-re)
>>(let ((org-link-abbrev-alist
>> (append org-link-abbrev-alist org-link-abbrev-alist-local)))
>> (org-link-open-from-string (match-string-no-properties 0
>> ...)
>> ...
>> What do you think?
>
> I do not like this
On Tue, Apr 26, 2022 at 11:54 AM Tim Visher wrote:
> I'm currently going to hack around it I think by simply making a function
> that updates the EXPORT_FILE_NAME property with the current heading text.
>
That's something like
```
(defun
Russell Adams writes:
>> > <2022-04-28 21:00>--<2022-04-29 02:00>
>>
>
> Is that technically a valid timestamp, meaning that it should be
> recognized? Or is it just Gnus outputting a bad timestamp and I should
> go try to adjust it?
It is valid. You can check it by calling M-:
Bastien writes:
> Ihor Radchenko writes:
>
>> If you confirm, I can just remove the call to `org-fold-reveal'.
>
> Yes, I do confirm -- thanks for the quick feedback.
Fixed in 4280762e4.
Best,
Ihor
David Masterson writes:
> Is it possible to setup a large (super-)agenda in outline form so that
> you can use the folding commands for focus in the Agenda view?
Could you elaborate?
There is org-agenda-entry-text-mode (E) and there is org-quick-peek
maybe doing something similar to what you
On Tue, Apr 26, 2022 at 05:43:48PM +0800, Ihor Radchenko wrote:
> Russell Adams writes:
>
> > --
> > * Fails w/o DOW, end time at 2100 not 0200
> >
> > <2022-04-28 21:00>--<2022-04-29 02:00>
>
> Confirmed.
>
> The problem is that org-ts-regexp1 does
This seems like something that could (should?) go in a personal config, as
a custom function, or advice.
You could, for example do something like this (lightly tested)
#+BEGIN_SRC emacs-lisp
(defun my-put (property value here)
(interactive (list nil nil current-prefix-arg))
(if (null here)
On Tue, Apr 26, 2022 at 08:17:23PM +0800, Ihor Radchenko wrote:
> Russell Adams writes:
>
> >> > <2022-04-28 21:00>--<2022-04-29 02:00>
> >>
> >
> > Is that technically a valid timestamp, meaning that it should be
> > recognized? Or is it just Gnus outputting a bad timestamp and I should
> > go
Russell Adams writes:
> What do you recommend as the next step?
org-ts-regexp1 should be fixed. But I currently have no ideas how. The
problem is caused by some edge case in Emacs regexp parser.
Best,
Ihor
Nick Dokos writes:
> The syntax is:
>
> #+BEGIN: clocktable ...
> #+END:
>
> There is no `clocktable' after `#+END:'.
Thanks for the patch! Could you please follow the commit summary
conventions described in
https://orgmode.org/worg/org-contribute.html#commit-messages?
Note that you
John Kitchin writes:
> This seems like something that could (should?) go in a personal config, as
> a custom function, or advice.
If it does not cost performance, I do not see any problem with adding
DWIM behaviour if point is inside drawer when calling org-set-property.
Best,
Ihor
Hi all,
Org speed commands are a major productivity boost and I love them.
Lately it has occurred to me to make some modifications with the
following configuration, which I share here in case someone wants to try
it. The idea is that Org speed commands are activated anywhere in the
header (not
Ignacio Casso writes:
> I agree that changing the current behavior of
> `org-link-open-from-string' may be problematic, however I don't think
> that it's worth to introduce the optional argument just for this
> "bug".
Makes sense. I am going ahead of what is currently on main.
> (cond
I'm Ok with this patch.
Haven't tested it myself, but looks good otherwise (probably Tim has
been using it for quite a while now)
Felipe
On 2022-04-23 09:29, Tim Van den Langenbergh wrote:
Felipe,
I have taken the liberty of reformatting the patch you created for ob-scheme.
You can find
`make test' has been failing for me with this error:
,
| Error: error ("Loading file
| /home/nick/src/emacs/org/org-mode/testing/lisp/test-ob-octave.el
| failed to provide feature ‘test-ob-octave’")
`
The attached patch provides a fix.
>From dc1ab2a24bfc5a02845c380c60f0c1a7452e639a Mon
I confirmed that an old emacs (25.1.50.1) running on Linux with an old
stock orgmode (8.2.10) does NOT exhibit the folding bug. The incorrect
behavior still happens on my up-to-date emacs/org (Org mode version
9.5.2 (release_9.5.2-25-gaf6f12 @
Ihor Radchenko writes:
> Nick Dokos writes:
>
>> The syntax is:
>>
>> #+BEGIN: clocktable ...
>> #+END:
>>
>> There is no `clocktable' after `#+END:'.
>
> Thanks for the patch! Could you please follow the commit summary
> conventions described in
>
Philip Kaludercic writes:
> Hi,
>
> I was wondering if someone could help me out to solve these annoyances I
> have been having with Org:
>
> 1. Most things I would like to clock are related to Emacs, but I often
>forget to check my agenda first, clock in, then clock out. Is there
>
Juan Manuel Macías writes:
> Org speed commands are a major productivity boost and I love them.
> Lately it has occurred to me to make some modifications with the
> following configuration, which I share here in case someone wants to try
> it. The idea is that Org speed commands are activated
fwiw, what i do is export to a buffer, then write to a file whose name
is derived from the header.
(alpha-make-valid-path
(with-current-buffer org-buffer
(org-get-heading 'no-tags 'no-todo)))
(defun alpha-make-valid-path (s)
"Make a string into a filesystem path."
;;
Ignacio Casso writes:
>> A better approach could be using org-link-expand-abbrev. It is an API
>> function and should be forward-compatible.
>
> Do you mean something like this?
>
> (defun org-open-at-point-global ()
> ...
> (cond ((org-in-regexp org-link-any-re)
>
Ihor Radchenko writes:
> Juan Manuel Macías writes:
>
>> Org speed commands are a major productivity boost and I love them.
>> Lately it has occurred to me to make some modifications with the
>> following configuration, which I share here in case someone wants to try
>> it. The idea is that
34 matches
Mail list logo
