From: Michael Brand <firstname.lastname@example.org> To: Carsten Dominik <email@example.com> Cc: Tassilo Horn <firstname.lastname@example.org>, email@example.com Subject: Re: bug#9695: allowed date range Date: Thu, 3 Nov 2011 18:22:51 +0100 [thread overview] Message-ID: <CALn3zog7PXkzD30Er8Ut-TpnnSJZDajW_F5g2ejGccqCE9oS4g@mail.gmail.com> (raw) In-Reply-To: <D5DADA52-90E0-4513-A501-E845169000D2@gmail.com> Hi Carsten On Thu, Oct 13, 2011 at 10:27, Carsten Dominik <firstname.lastname@example.org> wrote: > I am attaching a patch which will make time stamps without a day name > like <2011-10-12> work correctly. Furthermore, pressing C-c C-c on > a time stamp will fill in or fix the day name. > > However, I am not sure if this patch is complete, or if it > has side effects. So it would be good if a few people could > apply it and test it during their daily work for a few weeks, > and then report problems in this thread. I wonder how C-c C-c with a prefix (supported are one to three C-u) on a time stamp in a table field is expected to behave. In my opinion it should not only adjust the day name but like before also evaluate the table formula which it does not now. If the user does not expect and check the missing logs of the table calculation update he might wrongly assume that it happened and assume that there has been just no change. Michael
next prev parent reply other threads:[~2011-11-03 17:22 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <email@example.com> 2011-10-12 6:53 ` Ivan Kanis 2011-10-13 7:28 ` Tassilo Horn 2011-10-13 7:48 ` Eric S Fraga 2011-10-13 7:57 ` Tassilo Horn 2011-10-13 8:02 ` Carsten Dominik 2011-10-13 10:15 ` Eric S Fraga 2011-10-13 8:27 ` Carsten Dominik 2011-10-13 10:14 ` Eric S Fraga 2011-10-13 13:04 ` Tassilo Horn 2011-10-16 13:45 ` Michael Brand 2011-11-09 18:18 ` Carsten Dominik 2011-11-09 21:32 ` Michael Brand 2011-11-03 17:22 ` Michael Brand [this message] [not found] ` <firstname.lastname@example.org> 2012-03-23 1:30 ` Glenn Morris
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=CALn3zog7PXkzD30Er8Ut-TpnnSJZDajW_F5g2ejGccqCE9oS4g@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: bug#9695: allowed date range' \ /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
Code repositories for project(s) associated with this 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).