#497 Syntax Highlighting Patterns for Specman "e"

closed-works-for-me
Program (402)
5
2005-11-12
2005-11-08
Anonymous
No

The e.pats which you propse for download under

www.nedit.org/ftp/contrib/highlighting/e.pats

does not work after importing in .nedit config file.

Error message: see attached file

thomas.ahrens@wanadoo.fr

Discussion

1 2 > >> (Page 1 of 2)
  • error message from nedit

     
    Attachments
  • Thorsten Haude
    Thorsten Haude
    2005-11-08

    Logged In: YES
    user_id=119143

    Works for me, that is, I don't get an error message while
    activating the language mode. Could you provide a short
    example of Specman/e for me to use, including a part
    triggering the subroutine call pattern?

    What is the result of 'nedit -V'?

     
  • Thorsten Haude
    Thorsten Haude
    2005-11-08

    • labels: 355501 --> Program
    • assigned_to: nobody --> yooden
     
  • hooge789
    hooge789
    2005-11-10

    Logged In: YES
    user_id=1376420

    Hello,

    Thanks for your help.

    I tried nedit -V command as you asked me. Using the help
    button in the gui I see that I use version

    NEdit Version 5.0.2
    March 11, 1998

    nedit -V
    NEdit: Unrecognized option -V
    Usage: nedit [-read] [-create] [-line n | +n] [-server]
    [-do command]
    [-tags file] [-tabs n] [-wrap] [-nowrap]
    [-autoindent]
    [-noautoindent] [-autosave] [-noautosave]
    [-rows n]
    [-columns n] [-font font] [-display
    [host]:server[.screen]
    [-geometry geometry] [-xrm resourcestring]
    [-svrname name]
    [-import file] [file...]

    Unfortunally I can not send you an e file. Any file is a
    confidential one. But I could send you .nedit file but I
    don't know where I can attach it. Please tell me.

    Thanx again,
    Thomas

     
  • Thorsten Haude
    Thorsten Haude
    2005-11-11

    Logged In: YES
    user_id=119143

    Your version of NEdit is ancient (that's why it didn't
    recognize the -V option). Consider upgrading to a current
    version.

    About the e file: Sorry, but I don't see the error you
    describe with a blank file, so the next step would be to add
    some content. Couldn't you just make something up? It
    doesn't have to be long or in fact even valid (I wouldn't
    notice the difference), just cover the pattern I mentioned.

     
  • hooge789
    hooge789
    2005-11-11

    Logged In: YES
    user_id=1376420

    What do you mean by blank file? I downloaded the error
    message file. It's a jpg file, a snapshot of the error message
    window of nedit. You can open it with any viewer. I think this
    file is the best base to understand the bug. I am still
    convinced that there is missing or additional character which
    causes an error. It would be helpful if I could send you
    my .nedit file but I think this is only possible by entering a
    new bug what is not a clean solution. Do you see a way to
    analyze what happend with my .nedit file after nedit -import
    e.pats command ?
    Upgrading to a higher version is not easy for me because in a
    big company as my one only the administrator can do
    upgrades.

     
  • Thorsten Haude
    Thorsten Haude
    2005-11-11

    Logged In: YES
    user_id=119143

    Yes, I know how to display a .jpg (imagine that). The
    problem is not to understand what's happening to you, but to
    reproduce it myself. This would help a lot to eventually fix
    the problem.

    A blank file is an e file without anything in it. I don't
    know the last thing about e, so I don't know how to create a
    dummy file to check on your problem.

    Your .nedit file is not particularly interesting because
    it's matching the ancient version of NEdit you use. Also, I
    can see from the error message that I use the same pattern
    (and it works for me). You may try something yourself
    though: Move ~/.nedit out of the way to get a clean slate,
    then import e.pats and see whether the error persists. If it
    does not, we could try to fix your ~/.nedit. (About
    uploading: If you had filed the bug non-anonymously, you'd
    be able to attach more files. Now SF has no way to detect
    that you are the submitter.)

    About upgrading: As you can see, your version of NEdit is
    from the last century. Maybe you can convince your admin
    that a new version would be useful for more people than just
    yourself. A lot has changed since 5.0.2, including the
    syntax highlighting engine. So much that I won't bother
    trying to fix a bug in this version.

    The only thing I can still think of short of your upgrading
    to a recent version is to check whether this works using an
    actual e file. Please provide one.

     
  • Scott Tringali
    Scott Tringali
    2005-11-11

    Logged In: YES
    user_id=11321

    Note: you don't need admin access to upgrade. Download a
    new copy, put it in your user directory, and run it. That's
    all. We designed nedit to run with zero "installation".

    Even if we did manage to fix this bug, you couldn't get the
    fix unless you upgraded anyway.

     
  • Tony Balinski
    Tony Balinski
    2005-11-12

    Logged In: YES
    user_id=618141

    The issue is that the \w escape sequence was only
    introduced after 5.0.2. This is why you are seeing the error
    message. I believe \w was implemented in 5.1. Certainly it
    first appears in CVS at the second revision of the file
    regularExp.c (1.2, Sep 9 22:18:27 2000); the first revision
    (1.1) of the file being the official 5.0.2 source.

    My advice: upgrade. Those macros you have will no doubt
    work with newer versions of NEdit.

     
  • Thorsten Haude
    Thorsten Haude
    2005-11-12

    Logged In: YES
    user_id=119143

    Thanks for your good memory, Tony.

    Thomas, you should still upgrade to a recent version, but
    you can somewhat fix the problem by replacing any \w in the
    pattern by
    [a-zA-Z0-9_]

     
1 2 > >> (Page 1 of 2)