From: Subrata Datta <neeam@yahoo.com>
To: "Dennis_Krøger" <dennis@ipl.dtu.dk>, sourcenav@sources.redhat.com
Subject: Re: Making directories for new projects
Date: Fri, 13 Apr 2001 08:16:00 -0000 [thread overview]
Message-ID: <20010413151635.83713.qmail@web11603.mail.yahoo.com> (raw)
In-Reply-To: <00e901c0c412$37c50c90$ce17a8c0@d>
>
> Aside from that, this is the coolest IDE I have EVER seen!!!
>
I agree when I first started a on project, all I was given huge
code and doc. Thanks to SN I figured out most of it myself. Great
work SN developers! Nonetheless I saw the following issues..
in the parser I tried to accomadate other files type like *.txt,
*.con .. It tooke .txt and but not *.con or other file types.
Pl. let me know if I'm missing something here.
SN 5.0 seems to be faster that SN4.5.2 but no faster that MS
visual C++ env.It would be nice to get SN5.0 to that point.
regards,
SD
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
prev parent reply other threads:[~2001-04-13 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 4:54 Dennis Krøger
2001-04-13 8:16 ` Subrata Datta [this message]
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=20010413151635.83713.qmail@web11603.mail.yahoo.com \
--to=neeam@yahoo.com \
--cc=dennis@ipl.dtu.dk \
--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).