public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Ralf Corsepius <corsepiu@faw.uni-ulm.de>
To: sourcenav@sources.redhat.com
Subject: [patch] Fix to PR #75
Date: Tue, 05 Jun 2001 09:17:00 -0000	[thread overview]
Message-ID: <3B1D065A.4120DA7C@faw.uni-ulm.de> (raw)

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

Hi,

The patch below is supposed to fix the problem I had filed to the
sourcenav bug database eariler today (PR #57).

It changes the "m4parser" to be more selective on files to be
treated as "m4".

Ralf

-- 
Ralf Corsepius 
Forschungsinstitut fuer Anwendungsorientierte Wissensverarbeitung
(FAW)
Helmholtzstr. 16, 89081 Ulm, Germany     Tel: +49/731/501-8690
mailto:corsepiu@faw.uni-ulm.de           FAX: +49/731/501-999  
http://www.faw.uni-ulm.de
sourcenav-010412-sn_prop.cfg.in.diff


[-- Attachment #2: sourcenav-010412-sn_prop.cfg.in.diff --]
[-- Type: text/x-diff, Size: 667 bytes --]

--- sourcenav-010412.orig/snavigator/etc/sn_prop.cfg.in	Sat Dec  2 03:18:26 2000
+++ sourcenav-010412/snavigator/etc/sn_prop.cfg.in	Tue Jun  5 15:28:43 2001
@@ -252,12 +252,12 @@
 
 # m4 configuration files
 
-set use_m4parser 0
+set use_m4parser 1
 
 if {$use_m4parser} {
 
 sn_add_parser m4 \
-        -suffix {*.m4 *.in *.am} \
+        -suffix {*.m4 *configure.in *configure.ac} \
         -brow_cmd $sn_path(bindir)/m4browser \
 	-high_cmd $sn_path(bindir)/m4browser
 
@@ -273,7 +273,7 @@
 }
 
 if {! $use_m4parser} {
-    append other_ext " *.m4 *.in *.am"
+    append other_ext " *.m4 *configure.in *configure.ac"
 }
 
 sn_add_parser others -suffix $other_ext

                 reply	other threads:[~2001-06-05  9:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3B1D065A.4120DA7C@faw.uni-ulm.de \
    --to=corsepiu@faw.uni-ulm.de \
    --cc=sourcenav@sources.redhat.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.
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).