I want to create a clocktable report for all items under a specific
heading, using the match keyword and the ITEM property. It appears
that matching items this way won't include any subheadings, therefore
not showing their times in the clocktable.
My guess would be that agenda and clocktable
On 2024-05-06, 17:55 +0700, Max Nikulin wrote:
> It seems my comments have led mostly to confusion rather than
> improvements. I am sorry for that. I have in mind 2 kind of links:
> - that may be handled solely by
> `shortdoc-display-group' with second argument.
> - that should cause
>
Ihor Radchenko writes:
> David Masterson writes:
>
>> Hmm. Couldn't get rx (or rx-to-string) to work for me. Kept getting an
>> error that a stringp was expected for the argument to :exclude. I tried
>> variations on:
>>
>> :exclude (rx-to-string (seq (or "init" "calendar-beorg") ".org"))
>
> Date: Tue, 7 May 2024 09:10:59 -0700
> Cc: yanta...@posteo.net, emacs-de...@gnu.org, emacs-orgmode@gnu.org
> From: Jim Porter
>
> On 5/7/2024 5:20 AM, Eli Zaretskii wrote:
> > I disagree. These functions are nowadays the basis of many
> > interactive features, and users are usually mightily
On 07/05/2024 20:09, Ihor Radchenko wrote:
Max Nikulin writes:
I consider the following as a kind of graceful degradation
(defun org-sort-function-fallback-downcase
(a b LOCALE IGNORE-CASE)
(if ignore-case
(string-collate-lessp (downcase a) (downcase b) locale ignore-case)
On 07/05/2024 21:25, Charles Millar wrote:
On 5/7/24 7:49 AM, Max Nikulin wrote:
On 07/05/2024 03:05, Charles Millar wrote:
(setq toconvert 5.000)
(number-to-string toconvert)
evaluates to "5".
I get "5.0" (Linux), so I suspect some mistake.
I am using Debian Testing, full upgrade as of
On 5/7/2024 5:20 AM, Eli Zaretskii wrote:
I disagree. These functions are nowadays the basis of many
interactive features, and users are usually mightily confused by the
fine print of what "at point" means technically in Emacs. The current
operation is much easier for users to grasp mentally
> > I hear you. The behavior should be changed so
> > that, in general, bounds-of-thing-at-point etc.
> > return nil when there is _no thing at point_,
> > including when point is after, including just
> > after, a thing but not on such a thing.
> >
> > There can be commands (and noncommand fns)
Forwarded Message
Subject: Re: Bug: Final zero after decimal point is stripped when inline
code evaluated
Date: Tue, 7 May 2024 10:25:05 -0400
From: Charles Millar
To: Max Nikulin
On 5/7/24 7:49 AM, Max Nikulin wrote:
On 07/05/2024 03:05, Charles Millar wrote:
I
Max Nikulin writes:
> I consider the following as a kind of graceful degradation
>
> (defun org-sort-function-fallback-downcase
> (a b LOCALE IGNORE-CASE)
> (if ignore-case
> (string-collate-lessp (downcase a) (downcase b) locale ignore-case)
>(string-collate-lessp a b locale
Does Woof catch this?
--
Bastien Guerry
> From: Drew Adams
> CC: "e...@gnu.org" ,
> "emacs-de...@gnu.org"
> ,
> "emacs-orgmode@gnu.org"
> Date: Tue, 7 May 2024 01:52:13 +
>
> I hear you. The behavior should be changed so
> that, in general, bounds-of-thing-at-point etc.
> return nil when there is _no thing
On 07/05/2024 03:05, Charles Millar wrote:
I appreciate that mathematically a trailing zero or zeros may be
non-significant; however, in my use case, i.e. correct format in a text,
they are necessary. Another example, in addition to my Dollars and cents
scenario, may be a table that that has
Ihor Radchenko writes:
> And they reverted the warning at the end.
> https://git.savannah.gnu.org/cgit/emacs.git/commit?id=d51de0c5d90117bc1dc4bc5bc700253d71cd4579
Yes, it makes sense.
--
Bastien Guerry
On 05/05/2024 18:59, Ihor Radchenko wrote:
Ihor Radchenko writes:
If a user access same files from Linux and macOS then it
may be really annoying to get different order of entries in agenda. For
most of Linux users it is better to use more smart
`string-collate-lessp'. Some care is required to
Ihor Radchenko writes:
>> ⛔ Warning (lexical-binding): File
>> /home/bzg/.emacs.d/org-clock-save.el lacks `lexical-binding'
>> directive on its first line
>>
>> The attached patch should fix this. Is it okay to add it to bugfix?
>
> I think that it is premature.
> This is a warning
David Masterson writes:
> Hmm. Couldn't get rx (or rx-to-string) to work for me. Kept getting an
> error that a stringp was expected for the argument to :exclude. I tried
> variations on:
>
> :exclude (rx-to-string (seq (or "init" "calendar-beorg") ".org"))
When you have '(:foo bar :baz
17 matches
Mail list logo
