From: Drew Adams <drew.adams@oracle.com>
To: Phil Sainty <psainty@orcon.net.nz>, 17401@debbugs.gnu.org
Cc: contact@zaneashby.co.nz
Subject: bug#17401: 24.4.50; Narrow to {region,page,defun} in an indirect clone buffer in the other window
Date: Sun, 4 May 2014 06:43:51 -0700 (PDT) [thread overview]
Message-ID: <a9c7b7a5-e7ab-480f-8d41-207456e502a5@default> (raw)
In-Reply-To: <53661891.40206@orcon.net.nz>
+1
next prev parent reply other threads:[~2014-05-04 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 10:38 bug#17401: 24.4.50; Narrow to {region,page,defun} in an indirect clone buffer in the other window Phil Sainty
2014-05-04 13:43 ` Drew Adams [this message]
2014-05-08 0:05 ` Lennart Borgman
2014-05-10 13:06 ` Phil Sainty
2014-05-10 20:57 ` Josh
2014-05-11 4:12 ` Drew Adams
2020-09-18 13:57 ` Lars Ingebrigtsen
2020-09-18 16:02 ` Drew Adams
2020-09-18 21:22 ` Zane Ashby
2020-09-19 14:14 ` Lars Ingebrigtsen
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=a9c7b7a5-e7ab-480f-8d41-207456e502a5@default \
--to=drew.adams@oracle.com \
--cc=17401@debbugs.gnu.org \
--cc=contact@zaneashby.co.nz \
--cc=psainty@orcon.net.nz \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).