all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Hendricks <michael@ndrix.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: "copyright-clerk@fsf.org" <copyright-clerk@fsf.org>,
	31139@debbugs.gnu.org
Subject: bug#31139: [PATCH] Document Narrow indicator in describe-mode
Date: Thu, 19 Apr 2018 14:38:08 +0000	[thread overview]
Message-ID: <CAFHuXuareqsU8NZ+QyakZOMo03piPsy6g5yKwje8i23A=tW=_A@mail.gmail.com> (raw)
In-Reply-To: <87po2vs85p.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 935 bytes --]

On Thu, Apr 19, 2018 at 6:16 AM Noam Postavsky <npostavs@gmail.com> wrote:

> Okay, I'm convinced.  I think adding a comment along the lines of
> "narrowing is not a minor mode, but its indicator is part of
> mode-line-modes", would be helpful in case someone tries to "fix" your
> change later.
>
> > +     (when (or (> (point-min) 1) (<= (point-max) (buffer-size)))
>
> You should use buffer-narrowed-p instead of checking point min & max
> here.
>

Sounds good.  I'll run Emacs with these changes over the weekend.  If
everything is solid, I'll reply with a final patch early next week.

Have you assigned copyright for Emacs?


I submitted my copyright assignment on April 11, 2018, but it sounds like
I'm not on the current copyright assignment list for some reason. I've cc'd
the FSF copyright clerk with whom I handled the assignment, in case he
knows what happened.  For reference, my RT number for the assignment
was 1287241.

[-- Attachment #2: Type: text/html, Size: 1627 bytes --]

  parent reply	other threads:[~2018-04-19 14:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 17:12 bug#31139: [PATCH] Document Narrow indicator in describe-mode Michael Hendricks
2018-04-12 23:36 ` Noam Postavsky
2018-04-17 18:59   ` Michael Hendricks
2018-04-19 12:16 ` Noam Postavsky
2018-04-19 13:08   ` Eli Zaretskii
2018-04-19 14:38   ` Michael Hendricks [this message]
2018-04-19 14:44     ` Eli Zaretskii
2018-04-24 15:00   ` Michael Hendricks
2018-05-05  9:44     ` Eli Zaretskii

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='CAFHuXuareqsU8NZ+QyakZOMo03piPsy6g5yKwje8i23A=tW=_A@mail.gmail.com' \
    --to=michael@ndrix.org \
    --cc=31139@debbugs.gnu.org \
    --cc=copyright-clerk@fsf.org \
    --cc=npostavs@gmail.com \
    /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.