all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bruno Barbier <brubar.cs@gmail.com>
To: Jean Louis <bugs@gnu.support>, Luca Ferrari <fluca1978@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: help in writing function to pop indirect buffer
Date: Fri, 27 Jan 2023 19:30:35 +0100	[thread overview]
Message-ID: <63d41646.5d0a0220.2018e.e402@mx.google.com> (raw)
In-Reply-To: <Y9FtHZX6a9veJvI/@protected.localdomain>

Jean Louis <bugs@gnu.support> writes:

> * Luca Ferrari <fluca1978@gmail.com> [2023-01-25 14:16]:
>> This almost works, but when the indirect buffer is popped, I do not
>> have syntax highlight while I have indentation and apparently all the
>> other Perl things.
>> How can I turn on syntax highlight?
>
> I can see error:
> Not enabling jit-lock: it does not work in indirect buffer
>
> but how to solve it, I do not know.
>

I'm getting the same warning, but fontification seems to work and is
updated in both buffers.

In case it matters, I'm using:
   GNU Emacs 29.0.60 (build 2, x86_64-pc-linux-gnu, X toolkit, cairo
   version 1.17.6) of 2023-01-24

Did you try using a bare emacs ? (emacs -Q)


> I find great what you are doing.

Me too. I've never used indirect buffers, but, your function looks very
useful to focus on several small parts of huge files.

Thanks!

Bruno



  parent reply	other threads:[~2023-01-27 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-25 11:13 help in writing function to pop indirect buffer Luca Ferrari
2023-01-25 17:55 ` Jean Louis
2023-01-26  6:45   ` Emanuel Berg
2023-01-27 18:30   ` Bruno Barbier [this message]
     [not found]   ` <notmuch-sha1-03eb8baf922f469fd287c8e7e6f142e660e155d3>
2023-01-28 11:59     ` Bruno Barbier
2023-01-30 13:30       ` Luca Ferrari
2023-01-30 18:38         ` Bruno Barbier
2023-01-31  7:36         ` Jean Louis
2023-09-07 12:53           ` Luca Ferrari
2023-01-28 13:20 ` Jean Louis

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=63d41646.5d0a0220.2018e.e402@mx.google.com \
    --to=brubar.cs@gmail.com \
    --cc=bugs@gnu.support \
    --cc=fluca1978@gmail.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.