From: Tim Johnson <tim@akwebsoft.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Viminfo for emacs
Date: Fri, 10 Apr 2020 15:43:32 -0800 [thread overview]
Message-ID: <76c5218e-09c7-1ecf-2de2-c0ba599fb0f4@akwebsoft.com> (raw)
In-Reply-To: <9564A988-F411-410C-A864-E6004B8A40F9@easesoftware.com>
On 4/10/20 1:42 PM, Perry Smith wrote:
> On Apr 10, 2020, at 2:35 PM, Bruno Félix Rezende Ribeiro <oitofelix@gnu.org> wrote:
>> Tim Johnson <tim@akwebsoft.com> writes:
>>
>>> On 4/8/20 5:37 PM, Bruno Félix Rezende Ribeiro wrote:
>>>> Hi Tim,
>>>> Tim Johnson <tim@akwebsoft.com> writes:
>>>>> I have recently put together a barebones terminal mode emacs with evil
>>>>> as part of a custom config that starts up at least as fast as vim.
>>>> If eventually your Emacs config becomes heavy, the way to go is running
>>>> Emacs as a server once at system start-up and then use emacsclient
>>>> thereafter. See (info "(emacs) Emacs Server").
>>> Thanks Bruno. I had thought of that, but can emacs/emacsclient be run
>>> as a terminal app?
>> Sure. In fact you can have any number of emacsclient instances
>> (text-based and graphical) simultaneously connected to the same emacs
>> server: sharing buffers, settings and functionality.
> On Linux, the default install for emacs uses GTK+. GTK+ has a bug,
> which is documented in the emacs code somewhere, that you can not
> close the X windows connection. The fix is to use emacs built with
> Lucid.
>
> So… if you go the route of emacs server but you discover that
> sometimes you emacs server dies for no reason, try switching to the
> Lucid version.
>
> This bites, in particular when you export DISPLAY to another X server
> that is no local.
That's a darn good tip. A preliminary google turns out issues with lucid
compiles and fontification with version ~24
Do you think that is still an issue with 26.3?
--
Tim
tj49.com
next prev parent reply other threads:[~2020-04-10 23:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 0:37 Viminfo for emacs Tim Johnson
2020-04-01 8:20 ` Štěpán Němec
2020-04-01 15:16 ` Tim Johnson
2020-04-01 16:44 ` Jude DaShiell
2020-04-01 16:57 ` Jude DaShiell
2020-04-01 22:14 ` Tim Johnson
2020-04-01 16:43 ` Jude DaShiell
2020-04-09 1:37 ` Bruno Félix Rezende Ribeiro
2020-04-09 2:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-09 3:01 ` Bruno Félix Rezende Ribeiro
2020-04-10 19:23 ` Tim Johnson
2020-04-10 19:25 ` Tim Johnson
2020-04-10 19:35 ` Bruno Félix Rezende Ribeiro
2020-04-10 21:42 ` Perry Smith
2020-04-10 23:43 ` Tim Johnson [this message]
2020-04-11 1:14 ` Perry Smith
2020-04-11 1:32 ` Perry Smith
2020-04-11 7:05 ` tomas
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=76c5218e-09c7-1ecf-2de2-c0ba599fb0f4@akwebsoft.com \
--to=tim@akwebsoft.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).