public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: leonp@plris.com
To: sourcenav@sourceware.cygnus.com
Subject: Small suggestion and question
Date: Sun, 01 Apr 2001 09:03:00 -0000	[thread overview]
Message-ID: <5.0.2.1.0.20010401175711.00a7dd60@plris.com> (raw)

Hello,
         I use the SN for cross development (this time under Win2K without 
CygWin).

1 - Suggestion:
         It seems to be comfortable to have the "build" window be open as a 
subwindow in text editor - it is always accessible and one can rebuild his 
target fast after any small changes.      What seems to be not so 
comfortable is:
         a) The necessity to confirm each change before build starts (may 
be by default, if I pressed "build" button - save).
         b) This "build" subwindow seems to occupy too much place with the 
information which isn't so necessary at the moment - build command, build 
directory, target. If you ask me, the result window with 3 buttons at the 
same horizontal level will be brilliant.

2 - Question:
         When I run SN under Win2K it is VERY slow, which, besides making 
the work nervous, causes SN errors. For example, pressing Ctrl-S and Ctrl-W 
sequentually, causes an error below. This effect doesn't occur when running 
under Linux on the same machine. Does somebody know any medicine to the 
problem?

Error:
wrong # ".multiwindow-2.nbook.nbframe.edit.paned.edit.edit.edit" does not exist
-----------------------------------------------------------
Comment:
-----------------------------------------------------------
Version:        4.5.2
-----------------------------------------------------------
Full Name:      Red Hat Embedded DevKit
-----------------------------------------------------------
Product Name:   :Source-Navigator
-----------------------------------------------------------
sn_home:        c:/program files/cygnus/sn452
pwd:            C:/AGM142CP/SOURCES
project_dir:    C:/AGM142CP/SOURCES
project_file:   C:/AGM142CP/SOURCES/ofp.proj
db created with SN version: 4.5.2
db project version: 41001
db_prefix:      .snprj/ofp
db-directory:   .snprj  mode: 040744    directory
.snprj/ofp.f:   mode: 0100644   size: 2048
.snprj/ofp.fu:  mode: 0100644   size: 4608
.snprj/ofp.fil: mode: 0100644   size: 37376
.snprj/ofp.iu:  mode: 0100644   size: 2560
.snprj/ofp.ma:  mode: 0100644   size: 14336
.snprj/ofp.gv:  mode: 0100644   size: 4096
.snprj/ofp.iv:  mode: 0100644   size: 7680
.snprj/ofp.cl:  mode: 0100644   size: 1024
.snprj/ofp.ctr: mode: 0100644   size: 0
.snprj/ofp.to:  mode: 0100644   size: 71168
.snprj/ofp.by:  mode: 0100644   size: 73216
.snprj/ofp.un:  mode: 0100644   size: 1024
.snprj/ofp.fd:  mode: 0100644   size: 3584
-----------------------------------------------------------
osVersion: 5.0 byteOrder: littleEndian machine: intel platform: windows os: 
Windows NT
-----------------------------------------------------------
Stack:
wrong # ".multiwindow-2.nbook.nbframe.edit.paned.edit.edit.edit" does not exist
     while invoking
"Sn_Syntax_Highlight -delall c++ 
.multiwindow-2.nbook.nbframe.edit.paned.edit.ed..."
     invoked from within
"Sn_Syntax_Highlight -delall $grp $editor 1.0 end"
     (object ".multiwindow-2.nbook.nbframe.edit.paned." method 
"Editor&@@UpdateHighlights" body line 35)
     invoked from within
"UpdateHighlights $run_parse"
     (object ".multiwindow-2.nbook.nbframe.edit.paned." method 
"Editor&@@color_file" body line 3)
     invoked from within
"color_file"
     (object ".multiwindow-2.nbook.nbframe.edit.paned." method 
"Editor&@@save_file" body line 56)
     invoked from within
".multiwindow-2.nbook.nbframe.edit.paned.edit.edit save_file"
     (command bound to event)




Thanks a lot.


Leon Pollak
leonp@plris.com

             reply	other threads:[~2001-04-01  9:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-01  9:03 leonp [this message]
2001-04-03 15:22 ` Mo DeJong

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=5.0.2.1.0.20010401175711.00a7dd60@plris.com \
    --to=leonp@plris.com \
    --cc=sourcenav@sourceware.cygnus.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).