all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: John Wiegley <jwiegley@gmail.com>,
	George Plymale II <georgedp@orbitalimpact.com>
Cc: 28598@debbugs.gnu.org
Subject: bug#28598: 25.3; Errors in narrowed buffers in CC-mode
Date: Mon, 25 Sep 2017 20:50:57 +0000	[thread overview]
Message-ID: <20170925205057.GB4651@ACM> (raw)
In-Reply-To: <m27ewmsm4b.fsf@newartisans.com>

Hello, John and George.

On Mon, Sep 25, 2017 at 10:51:00 -0700, John Wiegley wrote:
> >>>>> "GP" == George Plymale <georgedp@orbitalimpact.com> writes:

> GP> For those too lazy to follow the link, here's the gist: When I press `RET'
> GP> at the beginning or end of a narrowed buffer in CC-mode, I see errors like
> GP> this:

> GP> c-determine-limit: Args out of range: #<buffer dired.c>, 1, 1564

> Alan, do you have any thoughts on this one?

Thanks for the heads up, John.

With the help of George's backtrace, I can see exactly what's happening,
where, and why.

The fixing of the bug will involve carefully defining conditions which
must hold when a function (c-determine-limit) is called, and amending it
on the assumption those conditions hold.

Give me a day or two, it's a bit late at the moment here in Germany.

> -- 
> John Wiegley                  GPG fingerprint = 4710 CF98 AF9B 327B B80F
> http://newartisans.com                          60E1 46C4 BD1A 7AC1 4BA2

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2017-09-25 20:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25  6:21 bug#28598: 25.3; Errors in narrowed buffers in CC-mode George Plymale II
2017-09-25 17:51 ` John Wiegley
2017-09-25 20:50   ` Alan Mackenzie [this message]
2017-09-26  1:14     ` George Plymale II
2017-10-01 18:55   ` Alan Mackenzie
2017-10-02 19:02     ` George Plymale II
2017-10-30 17:37       ` Alan Mackenzie

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=20170925205057.GB4651@ACM \
    --to=acm@muc.de \
    --cc=28598@debbugs.gnu.org \
    --cc=georgedp@orbitalimpact.com \
    --cc=jwiegley@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.