[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Viminfo for emacs
From: |
Perry Smith |
Subject: |
Re: Viminfo for emacs |
Date: |
Fri, 10 Apr 2020 20:32:55 -0500 |
> On Apr 10, 2020, at 8:14 PM, Perry Smith <pedz@easesoftware.com> wrote:
>
>
>
>> On Apr 10, 2020, at 6:43 PM, Tim Johnson <tim@akwebsoft.com> wrote:
>>
>> 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?
>
> Its not an emacs bug actually but a GTK+ bug. It bit me June 2019 (give or
> take)
> and I remember trying the latest / greatest emacs at that time (which was not
> the standard package on Ubuntu at the time).
>
> Shamefully… I vaguely remember tracking this down before :-( The bug is
> many years old.
>
> I no longer am using that particular set up.
>
> I would suggest use the standard emacs and see if you get hit by the bug
> and if you do, try Lucid. Perhaps others can chime in about the fortification
> issues you mention.
http://git.savannah.gnu.org/cgit/emacs.git/tree/src/xterm.c#n10058
<http://git.savannah.gnu.org/cgit/emacs.git/tree/src/xterm.c#n10058>
- Re: Viminfo for emacs, (continued)
- Re: Viminfo for emacs, Jude DaShiell, 2020/04/01
- Re: Viminfo for emacs, Bruno Félix Rezende Ribeiro, 2020/04/08
- Re: Viminfo for emacs, Emanuel Berg, 2020/04/08
- Re: Viminfo for emacs, Tim Johnson, 2020/04/10
- Re: Viminfo for emacs, Bruno Félix Rezende Ribeiro, 2020/04/10
- Re: Viminfo for emacs, Perry Smith, 2020/04/10
- Re: Viminfo for emacs, Tim Johnson, 2020/04/10
- Re: Viminfo for emacs, Perry Smith, 2020/04/10
- Re: Viminfo for emacs,
Perry Smith <=
- Re: Viminfo for emacs, tomas, 2020/04/11