emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Faryna <adamfaryna@gmail.com>
To: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: [feature request] org-at-timestamp-p should accept multiple parameters
Date: Tue, 8 Sep 2020 14:28:06 +0100	[thread overview]
Message-ID: <CABEF3YED9NCaNOFaWyE4gfcUfbFV5A_DeC4hF0XkCneWmXGuYA@mail.gmail.com> (raw)
In-Reply-To: <87v9gse5ve.fsf@bzg.fr>

[-- Attachment #1: Type: text/plain, Size: 748 bytes --]

I think the problem is general. If you work with any timestamp that is
agenda like, you can't check using this function if it's active or
inactive. The one solution would be to remove parameter "agenda" and
consider every timestamp as a agenda like (the "timestamp" in "
org-at-timestamp-p" suggest that there is time information in it anyway) by
default, or keep it as it is but extend parameter list with support of
named parameters where agenda-like can be activated with :agenda t,
inactive timestamp with :inactive t, with default values nil.

Thanks,
Adam

On Sat, 5 Sep 2020 at 13:59, Bastien <bzg@gnu.org> wrote:

> Hi Adam,
>
> you forgot to copy the emacs-orgmode list - can you repost your email
> there?
>
> Thanks,
>
> --
>  Bastien
>

[-- Attachment #2: Type: text/html, Size: 1158 bytes --]

  parent reply	other threads:[~2020-09-08 13:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-02 10:54 [feature request] org-at-timestamp-p should accept multiple parameters Adam Faryna
2020-09-05  8:31 ` Bastien
     [not found]   ` <CABEF3YFSNh8avFYjTSQ-Eww2qRAxt7+6OWHzjy25Ncd1MTgXkA@mail.gmail.com>
     [not found]     ` <87v9gse5ve.fsf@bzg.fr>
2020-09-08 13:28       ` Adam Faryna [this message]
2020-09-08 14:26         ` Bastien
2020-09-08 15:57           ` Adam Faryna
2020-09-09  8:13             ` Bastien
2020-09-09 11:04               ` Adam Faryna

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABEF3YED9NCaNOFaWyE4gfcUfbFV5A_DeC4hF0XkCneWmXGuYA@mail.gmail.com \
    --to=adamfaryna@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).