Re: Emacs lilypond-mode and also point-and-click

No, it was truncated, but in a hard to understand way - quite irregular. But we now know that was an artefact of the narrowing issue, and has not occurred again. Widening did not help. Andrew > On 16 Oct 2015, at 16:45, T. Michael Sommers wrote: > > When the buffer was

Re: Emacs lilypond-mode and also point-and-click

Quoting Andrew Bernard (andrew.bern...@gmail.com): > No, it was truncated, but in a hard to understand way - quite irregular. But > we > now know that was an artefact of the narrowing issue, and has not occurred > again. Widening did not help. Terms are important here. There's a world of

Emacs lilypond-mode and also point-and-click

Greetings All, I’m aware that the emacs lilypond-mode needs attention, but I wonder if anybody has seen this. When I enter a ‘>’ character to complete a chord, emacs goes into narrow mode, which then has to be undone with C-x n w. It’s consistently reproducible. Also, using evince on Ubuntu

Re: Emacs lilypond-mode and also point-and-click

Andrew Bernard writes: > Greetings All, > > I’m aware that the emacs lilypond-mode needs attention, but I wonder > if anybody has seen this. When I enter a ‘>’ character to complete a > chord, emacs goes into narrow mode, which then has to be undone with > C-x n w. It’s

Re: Emacs lilypond-mode and also point-and-click

Quoting Andrew Bernard (andrew.bern...@gmail.com): > Also, using evince on Ubuntu 15.04 with either Unity or the GNOME 3 Shell, > after several successful point-and-click redirects, the file in emacs get > messed up and the source file has to be reloaded. "messed up" is a bit vague. Is it

Re: Emacs lilypond-mode and also point-and-click

On 10/15/2015 7:24 AM, Andrew Bernard wrote: I’m aware that the emacs lilypond-mode needs attention, but I wonder if anybody has seen this. When I enter a ‘>’ character to complete a chord, emacs goes into narrow mode, which then has to be undone with C-x n w. It’s consistently reproducible.

Re: Emacs lilypond-mode and also point-and-click

Greetings All, With the fi, or workaround, for the narrowing problem, in place, the issue I reported regarding the emacs buffer being messed up (apologies for my lack of technical precision there! The buffer was being truncated to almost half the length in a way quite hard to figure out from

Re: Emacs lilypond-mode and also point-and-click

Greetings T.M., Commenting out these lines fixes the issue. Thanks! Can some elisp expert have a look at addressing this? For now, I am fine, but this must affect others I would think, unless there is something odd about my emacs setup, which is very simple. Should this be reported as a bug?

Re: Emacs lilypond-mode and also point-and-click

On 10/15/2015 10:28 PM, Andrew Bernard wrote: With the fi, or workaround, for the narrowing problem, in place, the issue I reported regarding the emacs buffer being messed up (apologies for my lack of technical precision there! The buffer was being truncated to almost half the length in a way

Re: Emacs lilypond-mode and also point-and-click

On Thu, Oct 15, 2015 at 8:03 AM, T. Michael Sommers wrote: > On 10/15/2015 7:24 AM, Andrew Bernard wrote: > >> >> I’m aware that the emacs lilypond-mode needs attention, but I wonder >> if anybody has seen this. When I enter a ‘>’ character to complete a >> chord, emacs

Re: Emacs lilypond-mode and also point-and-click

Steve Lacy writes: > On Thu, Oct 15, 2015 at 8:03 AM, T. Michael Sommers > wrote: > >> On 10/15/2015 7:24 AM, Andrew Bernard wrote: >> >>> >>> I’m aware that the emacs lilypond-mode needs attention, but I wonder >>> if anybody has seen this. When I enter a