[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [PATCH] Option for clock and timer to be displayed in frame-titl
Re: [O] [PATCH] Option for clock and timer to be displayed in frame-title
Tue, 06 Mar 2012 12:43:06 -0500
Gnus/5.110018 (No Gnus v0.18) Emacs/23.2 (gnu/linux)
Bernt Hansen <address@hidden> writes:
> Bernt Hansen <address@hidden> writes:
>> George Kettleborough <address@hidden> writes:
>>> On Tue, Feb 28 2012, Bernt Hansen wrote:
>>>> This patch needs a changelog entry in the commit text and a long
>>>> description would also be appreciated. The long description allows us
>>>> to see the purpose of the patch and how to use it without the necessity
>>>> to read and parse any of the code changes.
>>> Ok, I've done a changelog entry. I hope this is what is expected.
>>> (Also fixed a minor bug in original patch and added better documentation
>>> to the new custom variable).
>>> The patch adds options to both org-clock and org-timer regarding how the
>>> current clock/timer is displayed. Currently they are both displayed in
>>> the mode line. This is not ideal since if you split your window
>>> horizontally then the mode line becomes quite short so often the clock
>>> is truncated and the timer might not even be visible.
>>> The new options control whether the clock/timer is displayed in the mode
>>> line and/or frame title. The frame title is usually wasted space for
>>> people running a graphical version of emacs so it is quite useful there
>>> I think.
>> Thanks! I use frames on Windows at work and no frames on Linux (in
>> xmonad) at home. I tend to run with emacs full screen so I haven't
>> my modeline is long enough for me -- but it will be interesting to see
>> how the frame title clock works.
> Hi George,
> I tried this patch at work and it hangs my Emacs session in Windows on
> startup. It's totally unresponsive and I have to kill the process with
> the task manager.
> I think there's an implementation problem here but I don't have any
> other useful information about what it might be.
Nevermind... it seems to be working on Windows now. I'm not sure what
happened the first time. I'll report any other issues I find with this.