public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: "Mark S. Lewis" <msl@NetEFX.com>
To: sourcenav@sources.redhat.com
Subject: Questions about source navigator project
Date: Tue, 17 Dec 2002 09:19:00 -0000	[thread overview]
Message-ID: <5.2.0.9.0.20021217091431.018fb808@mail.NetEFX.com> (raw)

Greetings:

First, I have been using this tool for several months. A big "thank you" 
for building it and making it available! Just a quick question or two.

1. Is there any development/maintenance going on with this project? If not, 
what is the plan for this project?

2. There is a bug I have noticed which seems significant to me. When using 
the built--in editor, I notice times that I copy something into the buffer. 
If I make no other changes, the editor doesn't seem to notice that I've 
changed the buffer and doesn't save the updated buffer. This has cause me 
to loose changes several times. The work-around is to make some other 
trivial change and then save the buffer. Any fix for this?

Thanks.

... Mark

http://www.NetEFX.com <<<==---- Software Development Services



             reply	other threads:[~2002-12-17 17:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-17  9:19 Mark S. Lewis [this message]
2002-12-17 19:34 ` Alexandre Jasmin

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.2.0.9.0.20021217091431.018fb808@mail.NetEFX.com \
    --to=msl@netefx.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).