When I type ‘\ c’, the agenda view limits to my (c)all tags. This is what I
expected to see.
When I type ‘\ ’, however, it limits to every tag *but* the empty tag.
This is the opposite of what I expect to see.
Emacs : GNU Emacs 28.2 (build 1, x86_64-apple-darwin22.5.0, Carbon Version 169
thank you. it looks like outline-hide-subtree is the only one i will
need to synchronously change, to an org-fold version.
On 6/11/23, Ihor Radchenko wrote:
> Samuel Wales writes:
>
>> in my old version, i am finding functions and variables named
>> outline-* that have no obvious org-*
Ihor Radchenko writes:
> David Masterson writes:
>
>> -To assist project planning, TODO items can be labeled with a date
>> -and/or a time. The specially formatted string carrying the date and
>> -time information is called a /timestamp/ in Org mode.
>> +To assist project planning, TODO items
Ihor Radchenko writes:
> David Masterson writes:
>
>> Thank you. I haven't "patched" anything on Savannah and assumed I might
>> have to do the GNU copyright assignment. For this, I thought it would
>> be easy for you.
>
> Yes and no. One of the things you get to do when creating a proper
Hello,
I am attaching an updated patch for ox-icalendar unscheduled and
repeating TODOs, incorporating some of Ihor's feedback to my RFC some
months ago.
Compared to my original RFC, here are the main changes:
- For unscheduled TODOs with repeating deadline, the deadline warning
days is used
[Adding Org ML back to CC]
Sebastian Wålinder writes:
>> May you elaborate about what kind of library you are referring to?
>> Please describe the actual problem you ran into.
> I'm using the AI API library `org-assistant`
> (https://github.com/tyler-dodge/org-assistant).
> The library uses
Sebastian Wålinder writes:
> It appears that indirect buffers duplicate the entire org element cache from
> the base buffer whenever created.
Not exactly. Only link to the cache root is copied and some cache
elements may not be garbage-collected.
> Running `memory-report` indicates that each
Hello!
It appears that indirect buffers duplicate the entire org element cache from
the base buffer whenever created.
Running `memory-report` indicates that each indirect buffer has the same memory
blueprint.
This becomes a massive issue with large org files.
My in my 160 000 line org file,
Ypo writes:
> I would like to remove every tag when changing to done state.
>
> This is not working:
>
> '(org-todo-state-tags-triggers '((done ("(.*)"
>
> This works though:
>
> '(org-todo-state-tags-triggers '((done ("Atag"
Yes, regexps are not supported in
Hi
I would like to remove every tag when changing to done state.
This is not working:
'(org-todo-state-tags-triggers '((done ("(.*)"
This works though:
'(org-todo-state-tags-triggers '((done ("Atag"
Best regards
On 2023-06-11 12:21, Ihor Radchenko wrote:
This is a bug. Fixed now, on main.
Thanks!
Samuel Wales writes:
> in my old version, i am finding functions and variables named
> outline-* that have no obvious org-* replacement. a few do, and a few
> can be substituted with no probable issues. here are examples of
> stuff i might in principle be running:
Almost all the org-*
Jens Schmidt writes:
> (setq org-adapt-indentation 'headline-data)
>
> Paste the following into a new org file, headline A being the on the
> first line:
>
> snip
> ** Headline A
>
>
>
> ** Headline B
>
>
>
> ** Headline C
> :properties:
>
David Masterson writes:
> I've updated my patch file taking into account what you mentioned and
> what I tested. Does this look all right?
Thanks! See inline comments below.
> -To assist project planning, TODO items can be labeled with a date
> -and/or a time. The specially formatted string
David Masterson writes:
>> Yes. Though it would be better to attach the diff with proper (.diff or
>> .patch) extension.
>
> I hope you saw that I provided a "patch,txt" file in a following message
> (forgot about the naming convention -- been a long time...)
Inline and attachment are both
Ihor Radchenko writes:
> David Masterson writes:
>
Maybe I'm not explicit enough. In section 8.1 of the Org 9.6 manual is
a subsection "Time/Date Range" that *implies* times are supported in
ranges by the use of words "time" and "timestamp" when, above, you're
saying they
16 matches
Mail list logo
