actually:
ts-down
deadline-down
scheduled-down
results in output:
scheduled-down
deadlie-down
ts-down
On 6/19/23, Samuel Wales wrote:
> if i put ts-down before deadline-down and scheduled-down, it shows up
> after deadline and before scheduled.
>
> ((agenda habit-down time-up tsia-down
if i put ts-down before deadline-down and scheduled-down, it shows up
after deadline and before scheduled.
((agenda habit-down time-up tsia-down ts-down deadline-down
scheduled-down category-up user-defined-up)
(todo category-up user-defined-up)
(tags category-up user-defined-up)
(search
Dear Orgers,
as I mentioned some time ago, I'm writing a custom exporter (actually,
a very thin wrapper around the HTML exporter). I'd like `org-html-link'
to add some class to the links it generates. Is that possible?
TIA,
--
Marcin Borkowski
http://mbork.pl
i don't do anything with visibility. make test seems ok in bugfix.
but perhaps it does not generate a comprehensive agenda, in which case
maybe --batch would cause the bug.
what i am going to try to do is just remove --batch and lower the
frame and try to get bugfix to work like main. this is
Ihor Radchenko writes:
> David Masterson writes:
>
>> I used C-c C-a to attach my patch to the message for you. I was looking
>> for the reverse to pull your patch out. When I read the message, the
>> patch was inlined, so I wasn't seeing any buttons(?) to pull it out with
>> and the Mime
Ihor Radchenko writes:
What about the following approach:
When converting from org-src buffer back to Org,
1. We do not touch the original indentation, except minimal common
indentation of the whole src code, respecting the src mode value of
`indent-tabs-mode'.
2. Minimal common
Ihor Radchenko writes:
> I do not mind falling back to ":memory:" when :db is not specified, but
> we should display a warning to notify the users. Maybe not as a warning
> every time src block is executed, but at least via org-lint.
>
> Rudolf, WDYT?
I am not a fan of making the use of
Sébastien Miquel writes:
> Ihor Radchenko writes:
>> I feel that we will be getting various edge cases like the original
>> report and like the one I made up above if we keep trying to convert
>> tabs/spaces. Just retaining the original code indentation will be much
>> more robust, IMHO.
>
>
Samuel Wales writes:
> the bug occurs in recent bugfix, but not recent main, so perhaps we
> could say that it is fixed in main but that the fix has not been
> applied to bugfix? [if only the fix were known.]
Maybe.
> does org testing use --batch?
Yup.
If you have time and interest, it would
Ihor Radchenko writes:
I feel that we will be getting various edge cases like the original
report and like the one I made up above if we keep trying to convert
tabs/spaces. Just retaining the original code indentation will be much
more robust, IMHO.
Python code being broken with the default
10 matches
Mail list logo
