emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alain.Cochard@unistra.fr
To: Ihor Radchenko <yantar92@posteo.net>
Cc: alain.cochard@unistra.fr, emacs-orgmode@gnu.org
Subject: Re: Use timestamp instead of time-stamp uniformly in Org (was: How to update a timestamp?)
Date: Mon, 13 Mar 2023 12:36:26 +0100	[thread overview]
Message-ID: <25615.2746.773491.214764@gargle.gargle.HOWL> (raw)
In-Reply-To: <878rg0ga9q.fsf@localhost>

Ihor Radchenko writes on Mon 13 Mar 2023 11:29:

 > Would you be interested to create a patch?

I wish I could, but it is beyond my ability: I am not an (e)lisp

EOST (École et Observatoire des Sciences de la Terre) 
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes   [bureau 110]  | Phone: +33 (0)3 68 85 50 44 
F-67084 Strasbourg Cedex, France     | [ slot available for rent ]

  reply	other threads:[~2023-03-13 11:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12 23:24 How to update a timestamp? Dieter Faulbaum
2023-03-13  9:02 ` Alain.Cochard
2023-03-13 11:29   ` Use timestamp instead of time-stamp uniformly in Org (was: How to update a timestamp?) Ihor Radchenko
2023-03-13 11:36     ` Alain.Cochard [this message]
2023-03-13 11:52       ` Ihor Radchenko
2023-04-30 11:52     ` Ihor Radchenko

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=25615.2746.773491.214764@gargle.gargle.HOWL \
    --to=alain.cochard@unistra.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \


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