Hello,
Ihor Radchenko writes:
> Check out org-agenda-skip-function (see A.7 Special Agenda Views section
> of the manual).
>
> Also, I am doing something similar in my personal config using
> SHOWFROMDATE property. See
> https://github.com/yantar92/emacs-config/blob/master/config.org#properties
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> Ihor, My new patch still have some issue in the 'fold state which I
>> added "FIXME" marker. Hope can get some solution from you.
>
> I will comment only on the first patch for now.
>
>> "EXPORT_OPTIONS" "EXPORT_TEXT"
> Thanks for reporting!
> Fixed on main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=2d3802658156153974f540877a82bf5a384a2ad4
Thanks that fix it for me too.
Charles
signature.asc
Description: PGP signature
Daniel Ortmann writes:
> What's up with this behavior? It began a couple of weeks ago. I have
> the load-path set immediately in my init.el followed by require org.
>
> Versions are:
>
> * GNU Emacs 29.0.50 (build 9, x86_64-pc-linux-gnu, GTK+ Version
> 3.22.30, cairo version 1.15.12) of
"Christopher M. Miles" writes:
> Ihor, My new patch still have some issue in the 'fold state which I
> added "FIXME" marker. Hope can get some solution from you.
I will comment only on the first patch for now.
> "EXPORT_OPTIONS" "EXPORT_TEXT" "EXPORT_FILE_NAME"
> "EXPORT_TITLE"
What's up with this behavior? It began a couple of weeks ago. I have
the load-path set immediately in my init.el followed by require org.
Versions are:
* GNU Emacs 29.0.50 (build 9, x86_64-pc-linux-gnu, GTK+ Version
3.22.30, cairo version 1.15.12) of 2022-09-14
* Org mode version 9.5.5
> The fix is in preparation, but obviously I had tested my patch
> incorrectly (i.e. I probably compiled and tested another code than the
> one I had patched).
OK, here's a better version. As you can see, it's not nearly as simple.
Stefan
>From 9cd41bcbb6ca6771bd4c79f8b9d07241c67250ea
Stefan Monnier writes:
>>> In my book step 3 above is a mistake (even if moved to step 2).
>> I am confused.
>> AFAIK, changing the load-path is a common way for users to install
>> packages manually.
>
> No, you're not confused, I just think that installing packages manually
> (including
Ihor Radchenko [2022-09-14 20:32:53] wrote:
> Stefan Monnier writes:
>> The patch below simply enables `lexical-binding` in all the test files.
>> As far as I can tell, it's all that's needed (beside a missing
>> `require`).
> Thanks, but the patch causes 23 tests to fail (running make test).
Karl Voit [2022-09-13 Tue 10:07] wrote:
> Is it only me who is thinking that a non-blocking cancelled checkbox
> state would be a good idea?
At first it makes sense, but we do have headlines and TODO keywords to
express different states, colors and even sets of states. This is just a
checklist
On 14 September 2022, Charles Philip Chan wrote:
I am seeing the same problem. However, it did not resolve for me after upgrading
the compat library to the current git version. I am still getting:
,
| Warning (emacs): Org version mismatch. Make sure that correct ‘load-path’ is
| set early
William Denton writes:
Hello,
> Yesterday I pulled the current source trees for Org and Emacs and compiled as
> I usually do ... and everything broke, with Org complaining about mixed
> versions, and all kinds of warnings and backtraces and "Invalid function:
> compat-declare-version" errors.
>
William Denton writes:
Hello,
> Yesterday I pulled the current source trees for Org and Emacs and compiled as
> I usually do ... and everything broke, with Org complaining about mixed
> versions, and all kinds of warnings and backtraces and "Invalid function:
> compat-declare-version" errors.
>
Hi,
The `org-insert-link' function has the `auto-desc' variable to suppress
user prompt for link description. It worked accordingly its intention
(as I understand it) a couple of months a decade ago, after that the
logic was broken. Actually the behavior is rather strange: users may
edit
>> In my book step 3 above is a mistake (even if moved to step 2).
> I am confused.
> AFAIK, changing the load-path is a common way for users to install
> packages manually.
No, you're not confused, I just think that installing packages manually
(including messing with `load-path` and writing
Karl Voit writes:
>> So, to me the main use case to have an explicit cancel, is when I have a
>> long list, and to remember that I stated it as "cancelled".
>> If we go that way, having no other nice idea at the moment, I quite like
>> the [C] which is explicit although language specific.
>
>
Angel de Vicente writes:
> As per the example I was giving, I don't want that entry to be scheduled
> for October 16 (and thus clutter my agenda view), I just want it to be
> visible in my Global TODO list from that date, so then, depending on how
> busy I'm around that date, then I can decide
Stefan Monnier writes:
> The patch below simply enables `lexical-binding` in all the test files.
> As far as I can tell, it's all that's needed (beside a missing
> `require`).
Thanks, but the patch causes 23 tests to fail (running make test).
Also, is there any reason why it was a plain diff?
Hello,
"Rohit Patnaik" writes:
>> (not a scheduled one, since I don't need to do it on a particular date)
>
> The `SCHEDULED' property is in fact the correct way to indicate that you wish
> to
> hide the task from the global to-do list until a particular date. `SCHEDULED'
> indicates the day
Hello,
Angel de Vicente writes:
> great. That looks very promising, and without the need to change the
> source code. I will try it later on and report back.
I ended up with this (and going back to unmodified source code for
org-super-agenda, and it now works beautifully.
,
| (setq
> (not a scheduled one, since I don't need to do it on a particular date)
The `SCHEDULED' property is in fact the correct way to indicate that you wish to
hide the task from the global to-do list until a particular date. `SCHEDULED'
indicates the day upon which you wish to start working on the
Hello,
Christophe Schockaert writes:
> If I am right (I am playing with the config, it’s not in my daily setup yet
> for
> now), I could achieve this by defining "org-agenda-custom-commands" as shown
> in
> the "Projects" example :
>
Hello,
I'm wondering if it is possible to have a TODO item, but to not show it
in the global TODO list until certain date?
For example: I need to get a new insurance for my motor bike, but
insurance companies will not give me a quote until October 16, so I
would like to create a TODO entry (not
23 matches
Mail list logo
