lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Getting point and click going with gvim on Alma Linux


From: David Wright
Subject: Re: Getting point and click going with gvim on Alma Linux
Date: Mon, 5 Sep 2022 15:13:41 -0500

On Tue 06 Sep 2022 at 03:27:46 (+1000), Andrew Bernard wrote:
> 
> I'll incorporate your suggestions. Note that this was specifically
> about gvim not vim, but I can add in vim as well, since it is so
> closely related. There's still stuff here that is not covered in the
> NR,. such as window focus with the mouse that I think is useful.
> However, looking more closely now at the NR it looks like this file
> was a waste of time, as it is all covered the now. [I wonder if some
> bits came from my original screed? :-)] I'm guilty of not reading the
> current NR closely. Incidentally I use EDITOR for everything, not a
> different editor for lilypond, but that's a valid point re LYEDITOR.
> My notes reflect my bias.

I added the note about vim partly because J Martin Rushton
mentioned running it as part of a non-Frescobaldi workflow.

BTW I was interpreting your NR to refer, sensu stricto, to
notation.pdf, and Usage to refer to usage.pdf. It strikes me
that the distinction might not be obvious in the web docs.

I omitted to add that the lilypond-invoke-editor.desktop that
one creates is a scratch file, which can be deleted once the
xdg-* commands have been run. The official LP docs suggest
creating it in /tmp but without mentioning that that usually
results in it being cleaned out at the next boot.

> The gvim annoying error message and press ENTER to continue is still
> not resolved even in version 9 but I am determined to find an answer
> even it it means patching the source code. Currently it really makes
> gvim much less felicitous than it ought to be for this application.
> 
> I don't know if it is worth mentioning but emacs on Alma Linux at
> least totally carks it when used in this manner with emacs as as
> server. But emacs has the courtesy to print out that this is a known
> bug, then promptly dies!

I have in my notes (written when Debian was two versions back):

  $ emacs
  ESC-x server-start

  (Don't run emacs --daemon as this seems to provoke an error
  (or unusual effect) at the present time which is stretch.)

As is well-known, without setting emacs to server-mode, every
point-and-click will open a new instance. However, you can type
ESC-x server-start   at any time in any one emacs instance
(ie only one server in operation at a time).

> But my notes are really redundant since the NR does cover pretty much
> all, so I guess the recommendation can be changed to RTNR. :-)

The boxed note in Usage (§4.1.1 page 43) should carry a warning
that every time, apart from the first, that you try to start a
new instance of emacs (eg to reply to an email, edit a file,
point-and-click, etc), you'll end up with a split screen and
a 4-line warning message—very tedious.

ISTR that we had fun with apparmor last time around. I'll have
to check whether bullseye has been configured such that you don't
notice it, or whether I just haven't set it up to enforce it.
There are always wrinkles.

Cheers,
David.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]