unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Michael Welsh Duggan <md5i@md5i.com>
Cc: 9560@debbugs.gnu.org
Subject: bug#9560: An exact recipe
Date: Wed, 19 Oct 2011 10:16:18 +0000	[thread overview]
Message-ID: <20111019101617.GA2445@acm.acm> (raw)
In-Reply-To: <87zkh54o3x.fsf@maru.md5i.com>

Hi, Michael.

On Wed, Oct 12, 2011 at 10:33:22PM -0400, Michael Welsh Duggan wrote:
> >>>From emacs -Q:

> Do NOT resize the frame.  The recipe includes C-v, which depends on the
> window (and hence frame) size.

> Load the following file:

[ .... ]


> Type:

>   M-x edit-kbd-macro RET y C-x e C-x h C-w C-x i

> When prompted, insert the following keyboard macro file:

[ .... ]


> Type:

>   C-c C-c

> You should be back at rwsiteinfo-backup.c.  Execute the macro using:

>   C-x e

> Then type:

>   TAB

OK, I've got about this far.  I've been busy getting 5.32.2 into XEmacs.
The first thing I'm going to do with this macro is replace the C-v's with
an equivalent number of C-n's, because my frames on a tty are a fixed 65
lines (not including mode line and minibuffer) high.  :-)

Emacs's facilities for keyboard macros are not comfortable.

> At this point, you should see the indentation move to just under the `o'
> in "flowtype:list".  This location is incorrect.  If you then do the
> following:

>   M-x set-variable RET c-echo-syntactic-information-p RET t RET TAB

> you will see that c-mode believes the syntax at that point to be
> topmost-intro-cont instead of the proper brace-list-entry.

> When you have solved this bug, please let me know if the solution has a
> reasonable chance of having solved the other problem that I have not
> been able to recreate reliably, which is getting "topmost-intro indent
> 0" instead of "statement indent 4" when in the middle of editing a
> function.  If these have little chance of being connected, I'll do my
> best to try to create that scenario again (no promises).

> -- 
> Michael Welsh Duggan
> (md5i@md5i.com)

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2011-10-19 10:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20 15:25 bug#9560: 24.0.50; c-mode syntax problems Michael Welsh Duggan
     [not found] ` <handler.9560.B.131653264320111.ack@debbugs.gnu.org>
2011-09-20 15:34   ` bug#9560: Acknowledgement (24.0.50; c-mode syntax problems) Michael Welsh Duggan
2011-10-02 18:24 ` bug#9560: A dribble file of an emacs -Q session that triggers the problem Michael Welsh Duggan
2011-10-10  4:15 ` bug#9560: Cache information during failure Michael Welsh Duggan
2011-10-13  2:33 ` bug#9560: An exact recipe Michael Welsh Duggan
2011-10-19 10:16   ` Alan Mackenzie [this message]
2011-10-19 13:45     ` Michael Welsh Duggan
2011-10-19 17:39       ` Alan Mackenzie
2011-10-20 11:42       ` Alan Mackenzie
2011-10-21  1:42         ` Michael Welsh Duggan
2011-10-22 11:26 ` bug#9560: Bug #9560 fixed 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

  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=20111019101617.GA2445@acm.acm \
    --to=acm@muc.de \
    --cc=9560@debbugs.gnu.org \
    --cc=md5i@md5i.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 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).