unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Lee <pete_lee@swbell.net>
Subject: Re: Slickedit features in Emacs?
Date: Wed, 21 May 2003 19:34:26 GMT	[thread overview]
Message-ID: <u7k8krt4s.fsf@swbell.net> (raw)
In-Reply-To: 87e77d96.0305211059.3e15858a@posting.google.com

>>>>> "Henrik" == Henrik Jönsson <henrik.jonsson@se.transport.bombardier.com> writes:

    Henrik> I just was on a demo for Visual SlickEdit here at my
    Henrik> company. I am impressed.  My initial question was of
    Henrik> course if the functions in Slickedit exists in emacs. Some
    Henrik> of them exists I know.

    Henrik> * Autocompletion of expressions. When the user write "if "
    Henrik> it expands automatically into a full if template. Can this
    Henrik> be done with skeletons?

    Henrik> * "Intellisense". I know that semantic can do something
    Henrik> like this, but does it work for everyday use? Has anyone
    Henrik> tried it?

I don't use either of the above two things in emacs so I won't comment
on them (but I'm fairly certain autocompletions - aliases in slickedit -
are doable in emacs.

    Henrik> * Dynamic Tagging. Go to the function declaration etc. I
    Henrik> haven't used tags that much.

I do use ctags.  It's not dynamic like it is with slickedit however
(although I'm sure someone smarter than me could find a hook to make
it so).

    Henrik> I don't want to abandon emacs because I use it for
    Henrik> calendar, diary, notes, etc. But for programming Slickedit
    Henrik> is very interresting.

I used Slickedit for about 2 and a half years.  It has some nice
features for programmers.  The things I miss are intellisense and the
dynamic tagging.  The things I don't miss are the excruciatingly slow
load times of large workspaces, the occasional crashes,
buggy inconsistencies in tag file creation, the slick-c language, the
performance price you paid for dynamic tagging on large workspaces, and
of course the hefty price tag.

Towards the end of my time with slickedit I was using WTL quite
heavily and the intellisense didn't work well with it, so with the
primary reason I was willing to dish out $$ gone, I decided to learn
Emacs.

I'm quite happy now with Emacs and couldn't see myself ever using any
other editor.

Your mileage may vary of course.

  parent reply	other threads:[~2003-05-21 19:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-21 18:59 Slickedit features in Emacs? Henrik Jönsson
2003-05-21 19:08 ` Phillip Lord
2003-05-21 19:29 ` Benjamin Rutt
2003-05-22  7:07   ` Henrik Jönsson
2003-05-22 12:38     ` Bruce Ashfield
2003-05-22 14:14     ` Stefan Monnier
2003-05-22 17:12     ` Peter Lee
2003-05-22 19:42       ` Mark Mynsted
2003-05-22 20:04         ` Peter Lee
2003-05-22 20:23           ` Kai Großjohann
2003-05-22 20:52           ` Mark Mynsted
2003-05-22 21:03             ` Stefan Monnier
2003-05-23 13:38               ` Mark Mynsted
2003-05-23 15:44                 ` Peter Lee
2003-05-21 19:34 ` Peter Lee [this message]
2003-05-21 19:38 ` Burton Samograd
2003-05-21 20:30 ` Stefan Monnier
2003-05-22 13:56   ` Benjamin Rutt
2003-05-21 20:53 ` Ole Laursen
2003-05-22 15:31 ` Kai Großjohann

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u7k8krt4s.fsf@swbell.net \
    --to=pete_lee@swbell.net \
    /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).