From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kyle Meyer <kyle@kyleam.com>
Subject: Re: org-timer-set-timer from any buffer
Date: Wed, 12 Feb 2020 01:14:12 +0000
Message-ID: <87o8u438uz.fsf@kyleam.com>
References: <CAC=rjb4AhG1pu0UB9S3H9nJBTjBL26kwMEOSu-UGmCck10GU8w@mail.gmail.com>
 <87k14tqgbm.fsf@gnu.org> <87ftfhjelj.fsf@kyleam.com> <87blq513dl.fsf@bzg.fr>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:44612)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <kyle@kyleam.com>) id 1j1gbe-0005T6-91
 for emacs-orgmode@gnu.org; Tue, 11 Feb 2020 20:14:23 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <kyle@kyleam.com>) id 1j1gbd-0007V5-3n
 for emacs-orgmode@gnu.org; Tue, 11 Feb 2020 20:14:21 -0500
In-Reply-To: <87blq513dl.fsf@bzg.fr>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org
Sender: "Emacs-orgmode"
 <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org>
To: Bastien <bzg@gnu.org>
Cc: ian martins <ianxm@jhu.edu>, emacs-orgmode@gnu.org

Bastien <bzg@gnu.org> writes:

> Kyle Meyer <kyle@kyleam.com> writes:
>
>> Ian already addressed it with the patch at
>> <https://lists.gnu.org/archive/html/emacs-orgmode/2019-11/msg00166.html>,
>> which was applied as 044e9718c (org-timer.el: Allow org-timer-set-timer
>> from non-Org buffers, 2019-11-16).
>
> Thanks!  I didn't read the whole thread as I should have, thanks for
> applying this.

It happened in a separate thread, so there wasn't much hope for it to be
linked up.  I should have sent a message here for posterity when I
applied the patch.