From: Drew Adams <drew.adams@oracle.com>
To: "angelomolina@tutanota.com" <angelomolina@tutanota.com>
Cc: "'Help-Gnu-Emacs \(help-gnu-emacs@gnu.org\)'" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Function for enabling or disabling emacs bars
Date: Sat, 5 Mar 2022 16:54:55 +0000 [thread overview]
Message-ID: <SJ0PR10MB548840473375070E37AF605EF3069@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <MxPlHf1--3-2@tutanota.com>
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
Enabling Emacs bars...
Haven't yet come across an Emacs bar.
But I like the idea! Easily customize crazily
concocted potables, engage the Doctor in deep
bar-room chit-chat,...
So I vote for _enabling_. With a GPL license,
of course. That's free for all.
___
No libation without representation!
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 13263 bytes --]
next prev parent reply other threads:[~2022-03-05 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 15:49 Function for enabling or disabling emacs bars angelomolina--- via Users list for the GNU Emacs text editor
2022-03-05 16:54 ` Drew Adams [this message]
[not found] ` <SJ0PR10MB548840473375070E37AF605EF3069@SJ0PR10MB5488.namprd10.prod.outlook.com-MxQ-TzU----2>
2022-03-05 17:14 ` [External] : " angelomolina--- via Users list for the GNU Emacs text editor
2022-03-14 15:02 ` GNU Hacker
2022-03-14 15:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-14 17:40 ` angelomolina--- via Users list for the GNU Emacs text editor
2022-03-14 17:55 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-14 20:00 ` GNU Hacker
[not found] ` <87ilsgi9sq.fsf@gnu.org-My90SEi----2>
2022-03-14 20:16 ` angelomolina--- via Users list for the GNU Emacs text editor
2022-03-14 22:08 ` GNU Hacker
2022-03-14 22:19 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-14 22:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB548840473375070E37AF605EF3069@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=angelomolina@tutanota.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.