From: Jean Louis <bugs@gnu.support>
To: 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: Sat, 28 Jan 2023 16:20:39 +0300 [thread overview]
Message-ID: <Y9UhJ6Uo6iBtaHqG@protected.localdomain> (raw)
In-Reply-To: <CAKoxK+6t6KBwevLqeCDyL5VQ6_N3XB7L1xC6rDXbX964LeJnLA@mail.gmail.com>
More information:
EmacsWiki: Indirect Buffers:
https://www.emacswiki.org/emacs/IndirectBuffers
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
prev parent reply other threads:[~2023-01-28 13:20 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
[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 [this message]
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=Y9UhJ6Uo6iBtaHqG@protected.localdomain \
--to=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.
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).