emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Faryna <adamfaryna@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [feature request] org-at-timestamp-p should accept multiple parameters
Date: Wed, 9 Sep 2020 12:04:59 +0100	[thread overview]
Message-ID: <CABEF3YGcZnpjhwb_dg0YqJBK8msgJzWrRxmN8c0yy5GQ38GYQg@mail.gmail.com> (raw)
In-Reply-To: <87tuw7mkow.fsf@gnu.org>

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

Thanks. I understand now.

I think to generate a patch in this case it's too much hustle, for a minor


On Wed, 9 Sep 2020 at 09:13, Bastien <bzg@gnu.org> wrote:

> Hi Adam,
> Adam Faryna <adamfaryna@gmail.com> writes:
> > Ok, maybe I misunderstood the purpose of this function. I wanted to
> > use it to check if the timestamp is active or inactive and I tried to
> > get it by using (org-at-timestamp-p 'inactive) while pointing at the
> > timestamp. But actually when I call it on any timestamp like
> > [2020-09-04 Fri], <2020-09-04 Fri> I always get nil. So either it's a
> > bug, or I miss something.
> (org-at-timestamp-p) returns t on an active timestamp.
> (org-at-timestamp-p 'inactive) returns t on any timestamp, including
> inactive ones.
> If you think the docstring could be enhanced, can you share a patch?
> See https://orgmode.org/worg/org-contribute.html on how to contribute.
> Thanks,
> --
>  Bastien

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

      reply	other threads:[~2020-09-09 11:05 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
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 [this message]

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:

  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=CABEF3YGcZnpjhwb_dg0YqJBK8msgJzWrRxmN8c0yy5GQ38GYQg@mail.gmail.com \
    --to=adamfaryna@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).