emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: Tim Ruffing <crypto@timruffing.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Don't reset `org-todo-keywords-for-agenda' when org-agenda-multi
Date: Fri, 10 Mar 2023 19:32:43 +0700	[thread overview]
Message-ID: <2295526f-b026-4721-bf82-2b422d5844c1@gmail.com> (raw)
In-Reply-To: <871qlwzv2k.fsf@localhost>

On 10/03/2023 18:48, Ihor Radchenko wrote:
> Tim Ruffing writes:
>> * org-agenda.el (org-prepare-agenda): Don't reset
>> `org-todo-keywords-for-agenda' when org-agenda-multi.

> Unfortunately, it does not apply.

- @@ lines are wrapped by mail user agent
- tabs are converted to spaces


While some people find it convenient to send patches as messages (and 
some projects require such format), for others it is easier to add an 
attachment than setting up mail client to avoid unintended modifications 
of patches.

  parent reply	other threads:[~2023-03-10 12:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 12:46 [PATCH] Don't reset `org-todo-keywords-for-agenda' when org-agenda-multi Tim Ruffing
2023-03-10 11:48 ` Ihor Radchenko
2023-03-10 12:08   ` Tim Ruffing
2023-03-10 12:32   ` Max Nikulin [this message]
2023-03-10 14:16     ` Tim Ruffing
2023-03-11 10:22       ` 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=2295526f-b026-4721-bf82-2b422d5844c1@gmail.com \
    --to=manikulin@gmail.com \
    --cc=crypto@timruffing.de \
    --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).