public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Syd Polk <spolk@redhat.com>
To: Ben Elliston <bje@redhat.com>
Cc: Mo DeJong <mdejong@cygnus.com>, sourcenav@sources.redhat.com
Subject: Re: Adding Ruby support to Source Navigator
Date: Mon, 13 Nov 2000 08:47:00 -0000	[thread overview]
Message-ID: <3A101BE4.129FADE4@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0011140103170.30281-100000@moshpit.cygnus.com>

Ben Elliston wrote:
> 
> Yo Mo,
> 
>    Well, are you going to be around to help keep it working? I don't know
>    that would have a problem with adding support for ruby, I just want to
>    make sure we don't end up with an abandoned parser. I know Ben was
>    thinking about what changes would be needed to move the syntax
>    highlighter out of the core, but he would know more about that.
> 
> I've already started -- I have the configury in place to build the syntax
> highlighters as shared libraries with libtool.  The next step is to just add
> in the hooks to load these libraries with Tcl's "load" command at start-up.
> 
> I'm trying to decide whether all libraries matching a specific pattern (say,
> "*high*.so" should be loaded, or whether they should be named explicitly in
> the configuration file.  Thoughts?

Hmm. I hate configuration files. I would vote for a pattern.

Something like:

sn*high*.so on unix

and

sn*high*.dll on windows.



> 
> At any rate, this'll be a vast improvement.
> 
> Ben

  reply	other threads:[~2000-11-13  8:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-10 13:25 Dave Thomas
2000-11-11 18:55 ` Mo DeJong
2000-11-13  6:05   ` Ben Elliston
2000-11-13  8:47     ` Syd Polk [this message]
2000-11-13 14:11       ` Ben Elliston
2000-11-13 14:28 Ian Roxborough

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=3A101BE4.129FADE4@redhat.com \
    --to=spolk@redhat.com \
    --cc=bje@redhat.com \
    --cc=mdejong@cygnus.com \
    --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).