From: Nathan Neff <nathan.neff@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Move Currently clocked in task to left on modeline
Date: Tue, 3 Sep 2019 22:53:11 -0500 [thread overview]
Message-ID: <CAC=HedBUt5QCia-cba_ORU3fyyVK4whZBV29QbPiD2grtGkJnQ@mail.gmail.com> (raw)
In-Reply-To: <875zntod0f.fsf@alphaville.usersys.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]
Thanks Nick,
Anyone else, I would like to hear how you can keep the currently clocked
task in plain site - I use MacOS and Linux, so if there's any OS-specific
status software that you recommend let me know.
Thanks,
--Nate
On Mon, Jul 22, 2019 at 6:39 PM Nick Dokos <ndokos@gmail.com> wrote:
> Nathan Neff <nathan.neff@gmail.com> writes:
>
> > Hello all,
> >
> > How can I move the currently clocked task to be on the left side
> > of my modeline in emacs?
> >
>
> The way the information ends up in the mode line is a bit convoluted:
>
> - The main variable is `mode-line-format': you should read its doc
> string carefully.
>
> - `mode-line-format' includes the variable `mode-line-misc-info'
> towards the end.
>
> - `mode-line-misc-info' includes the variable `global-mode-string'
> (in a somewhat peculiar way that I don't quite understand).
>
> - `org-clock-in', `org-clock-out' and `org-clock-cancel' affect the
> mode line by modifying the `global-mode-string' variable to append
> or delete `org-mode-line-string' to/from it and then forcing a
> mode-line update with (drum roll) `force-mode-line-update'.
>
> - The rest of the org mode code mucks around with `org-mode-line-string'
> exclusively.
>
> In short, there is no way to change the position of the currently
> clocked task without rewriting code. You might be able to move
> *all* of the org information by modifying an earlier mode-line
> component (rather than `global-mode-string' which is part of the
> final component). But it would not be trivial.
>
> --
> Nick
>
> "There are only two hard problems in computer science: cache
> invalidation, naming things, and off-by-one errors." -Martin Fowler
>
>
>
[-- Attachment #2: Type: text/html, Size: 2395 bytes --]
prev parent reply other threads:[~2019-09-04 3:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 22:35 Move Currently clocked in task to left on modeline Nathan Neff
2019-07-22 23:39 ` Nick Dokos
2019-09-04 3:53 ` Nathan Neff [this message]
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='CAC=HedBUt5QCia-cba_ORU3fyyVK4whZBV29QbPiD2grtGkJnQ@mail.gmail.com' \
--to=nathan.neff@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.com \
/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
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
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).