From: pietru@caramail.com
To: pietru@caramail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: Toggle appointment notification
Date: Wed, 2 Dec 2020 16:15:10 +0100 [thread overview]
Message-ID: <trinity-4612eb57-732f-49a2-97bf-5dc8c184358f-1606922110232@3c-app-mailcom-bs14> (raw)
In-Reply-To: <trinity-9d11ddea-96be-4af9-813e-bbd3950ccc36-1606921230550@3c-app-mailcom-bs14>
And if I also have notification enabled, the problem gets even
worse. Looks like one has to also do the same for every major
mode. Seems to be a complicated thing to do. I could simply
have an emacs session used only for appointment notification.
> Sent: Wednesday, December 02, 2020 at 4:00 PM
> From: pietru@caramail.com
> To: pietru@caramail.com
> Cc: tomas@tuxteam.de, help-gnu-emacs@gnu.org
> Subject: Re: Toggle appointment notification
>
> I want to use (display-time), but is it possible to remove
> [(Lisp Interaction AC MS ElDoc)] from the mode line? Because
> my screen is not very wide.
>
> Many Thanks.
>
>
> > Sent: Tuesday, December 01, 2020 at 8:58 PM
> > From: pietru@caramail.com
> > To: tomas@tuxteam.de
> > Cc: help-gnu-emacs@gnu.org
> > Subject: Re: Toggle appointment notification
> >
> > > Sent: Tuesday, December 01, 2020 at 8:53 PM
> > > From: tomas@tuxteam.de
> > > To: help-gnu-emacs@gnu.org
> > > Subject: Re: Toggle appointment notification
> > >
> > > On Tue, Dec 01, 2020 at 10:23:31PM +0300, Jean Louis wrote:
> > > > * pietru@caramail.com <pietru@caramail.com> [2020-12-01 22:14]:
> > > > > > (defun message-any (any)
> > > > > > "Message anything to minibuffer"
> > > > > > (message "%s" (prin1-to-string any)))
> > > > >
> > > > > How can one add a heading string before calling prin1-to-string.
> > > > > The message would then give me some more clarity.
> > > >
> > > > (message "%s: %s" heading (prin1-to-string any))
> > >
> > > Or, if the heading is a constant, just
> > >
> > > (message "my heading: %s" (prin1-to-string any))
> >
> > Super
> >
> > > Cheers
> > > - t
> > >
> >
> >
>
next prev parent reply other threads:[~2020-12-02 15:15 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 3:47 Toggle appointment notification pietru
2020-12-01 4:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-01 5:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-01 18:35 ` pietru
2020-12-01 18:52 ` Jean Louis
2020-12-01 19:01 ` pietru
2020-12-01 19:13 ` pietru
2020-12-01 19:23 ` Jean Louis
2020-12-01 19:38 ` pietru
2020-12-01 19:53 ` tomas
2020-12-01 19:58 ` pietru
2020-12-02 15:00 ` pietru
2020-12-02 15:15 ` pietru [this message]
2020-12-02 15:47 ` Michael Heerdegen
2020-12-02 15:58 ` pietru
2020-12-02 17:39 ` pietru
2020-12-02 17:46 ` pietru
2020-12-03 1:39 ` Michael Heerdegen
2020-12-03 2:18 ` pietru
2020-12-03 22:32 ` Michael Heerdegen
2020-12-03 1:50 ` Michael Heerdegen
2020-12-03 2:14 ` pietru
2020-12-03 3:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-03 4:06 ` pietru
2020-12-03 4:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-03 22:38 ` Michael Heerdegen
2020-12-12 1:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 1:26 ` Christopher Dimech
2020-12-12 1:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 1:48 ` Christopher Dimech
2020-12-12 1:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 1:59 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 3:55 ` Michael Heerdegen
2020-12-12 4:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 22:42 ` Michael Heerdegen
2020-12-17 4:31 ` Michael Heerdegen
2020-12-03 2:17 ` daniela-spit
2020-12-03 3:19 ` Pankaj Jangid
2020-12-03 5:35 ` pietru
2020-12-03 15:19 ` pietru
2020-12-03 17:09 ` Jean Louis
2020-12-03 17:20 ` pietru
2020-12-03 17:58 ` Jean Louis
2020-12-03 18:29 ` pietru
2020-12-03 19:41 ` Jean Louis
2020-12-03 19:58 ` Jean Louis
2020-12-03 20:23 ` pietru
2020-12-03 20:38 ` Jean Louis
2020-12-03 21:30 ` Christopher Dimech
2020-12-03 22:43 ` Arthur Miller
2020-12-03 22:51 ` Christopher Dimech
2020-12-03 23:12 ` Michael Heerdegen
2020-12-03 23:03 ` Michael Heerdegen
2020-12-03 23:49 ` Jean Louis
2020-12-04 0:28 ` pietru
2020-12-04 5:59 ` Jean Louis
2020-12-04 6:28 ` pietru
2020-12-04 7:11 ` Jean Louis
2020-12-03 23:59 ` pietru
2020-12-04 1:13 ` Michael Heerdegen
2020-12-04 1:39 ` pietru
2020-12-03 10:19 ` Jean Louis
2020-12-01 21:44 ` Michael Heerdegen
2020-12-02 8:41 ` tomas
2020-12-02 12:05 ` Christopher Dimech
2020-12-02 12:37 ` tomas
2020-12-02 13:15 ` Christopher Dimech
2020-12-02 13:52 ` tomas
2020-12-02 14:10 ` Christopher Dimech
2020-12-02 14:20 ` Robert Pluim
2020-12-02 15:04 ` Christopher Dimech
2020-12-02 15:08 ` Jean Louis
2020-12-02 21:14 ` tomas
2020-12-02 21:41 ` Jean Louis
2020-12-02 22:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-02 22:54 ` Jean Louis
2020-12-02 15:25 ` Drew Adams
2020-12-02 15:04 ` Jean Louis
2020-12-02 1:54 ` daniela-spit
2020-12-02 2:47 ` Michael Heerdegen
2020-12-02 3:04 ` daniela-spit
2020-12-02 3:23 ` Michael Heerdegen
2020-12-02 4:16 ` daniela-spit
2020-12-02 4:26 ` daniela-spit
2020-12-02 4:59 ` Jean Louis
2020-12-01 9:13 ` Andreas
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-4612eb57-732f-49a2-97bf-5dc8c184358f-1606922110232@3c-app-mailcom-bs14 \
--to=pietru@caramail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).