all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jeff Dwork" <jeff.dwork@amd.com>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: No matching closing block
Date: Wed, 28 Jun 2006 14:16:09 -0700	[thread overview]
Message-ID: <17570.61849.865044.601781@lx-deskh181.amd.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0606270829001.25884@bugs.unl.edu.ar>

Customize blink-matching-paren-distance to increase the search range
for the open {

Jeff

Martin Marques writes:
 > To: bug-gnu-emacs@gnu.org
 > Subject: No matching closing block
 > Date: Tue, 27 Jun 2006 08:35:13 -0300 (ART)
 > 
 > I'm not sure this is a bug, but I'll try to explain what I found.
 > 
 > I have program written in PHP (using php-mode) and when ever I'm over the 
 > 1000 lines inside an open {, the closing } doesn't show where the block 
 > started. If I'm within the 1000 lines (block has less then 1000 lines) it 
 > shows in the minibuffer where the block started.
 > 
 > versions:
 > 
 > $ dpkg -l | grep -i emacs
 > ii  emacs21                       21.4a-3               The GNU Emacs 
 > editor
 > ii  emacs21-bin-common            21.4a-3               The GNU Emacs 
 > editor's shared, architecture
 > ii  emacs21-common                21.4a-3               The GNU Emacs 
 > editor's shared, architecture
 > ii  emacsen-common                1.4.17                Common facilities 
 > for all emacsen
 > ii  php-elisp                     1.1.0-2               Emacs support for 
 > php files
 > 
 > 
 > I hope I was clear. If you need any debugging, feel free to ask.
 > 
 > --
 >   21:50:04 up 2 days,  9:07,  0 users,  load average: 0.92, 0.37, 0.18
 > ---------------------------------------------------------
 > Lic. Martín Marqués         |   SELECT 'mmarques' || 
 > Centro de Telemática        |       '@' || 'unl.edu.ar';
 > Universidad Nacional        |   DBA, Programador,
 >      del Litoral             |   Administrador
 > ---------------------------------------------------------_______________________________________________
 > bug-gnu-emacs mailing list
 > bug-gnu-emacs@gnu.org
 > http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs

-- 
Jeff Dwork                     | jeff.dwork@amd.com  408-307-2496 (cell)
Advanced Micro Devices, M/S 362| 408-749-5216 (desk) 408-774-7811 (fax)
PO Box 3453                    |----------------------------------------
Sunnyvale, Ca 94088-3453       | 

      parent reply	other threads:[~2006-06-28 21:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 11:35 No matching closing block Martin Marques
2006-06-28 20:29 ` Kevin Rodgers
2006-06-28 21:16 ` Jeff Dwork [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17570.61849.865044.601781@lx-deskh181.amd.com \
    --to=jeff.dwork@amd.com \
    --cc=bug-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.
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.