tobeye@NORTHSTAR.DARTMOUTH.EDU (Anthony Edwards) (05/26/90)
While I'm making suggestions, I might as well mention something that
I've put up with for a while...
Has anyone noticed how ctext auto-indent feature continues to work even
inside comment blocks? This is annoying because ctext wants semi-colons
at the end of the line in order to line up with the line above it.
However, I very rarely add semi-colons to the end of my lines in a
comment! What tends to happen is that ctags indents 2 more spaces for
the 2nd+ line of a comment. However, as I use other puncutation (most
particularly open
parenthesis toward the end of a line), ctext indents even more.
REALLY, when I'm in a comment, I just want the lines to line up below
each other. (While enhanhing this, it would be nice if comments
automatically added the next '*' on the next line, too, but that would
be for bonus points). Try typing this comment using ctext:
/* This is just a C comment. Nothing fancy -
it just has some general text (and perhaps
one note in parenthesis, too)
*/
You'll see that 'it' appears indented 2 characters over. You'll see
that "one note" is very far over to the right, starting just after the
'('. It looks like this:
/* This is just a C comment. Nothing fancy -
it just has some general text (and perhaps
one note in parenthesis, too)
*/
Ideally, I'd like to to do this:
/* This is just a C comment. Nothing fancy -
* it just has some general text (and perhaps
* one note in parenthesis, too)
*/
- Anthony Edwardstom@ICASE.EDU (Tom Crockett) (05/29/90)
Excerpts from internet.info-andrew: 25-May-90 ctext suggestion Anthony Edwards@northsta (1498+0) > (While enhanhing this, it would be nice if comments automatically added > the next '*' on the next line, too, but that would be for bonus points). Please, no! It may fit your coding style, but it doesn't fit mine!
cmf@UNIX.CIS.PITT.EDU ("Carl M. Fongheiser") (05/29/90)
Excerpts from info-andrew: 29-May-90 Re: ctext suggestion Tom Crockett@icase.edu (312+0) > Excerpts from internet.info-andrew: 25-May-90 ctext suggestion Anthony > Edwards@northsta (1498+0) >> (While enhanhing this, it would be nice if comments automatically added >> the next '*' on the next line, too, but that would be for bonus points). > Please, no! It may fit your coding style, but it doesn't fit mine! It would be *really* nice if these things were configurable, ala C-mode in a certain other editor that vaguely resembles ez :-) Carl Fongheiser cmf@unix.cis.pitt.edu
Craig_Everhart@TRANSARC.COM (05/29/90)
One way of doing comments in ctext is simply to type everything on one line. I use it all the time and haven't yet found a C compiler that complains about very long lines, all of which is a comment. > Excerpts from internet.info-andrew: 25-May-90 ctext suggestion Anthony > Edwards@northsta (1498+0) > /* This is just a C comment. Nothing fancy - > it just has some general text (and perhaps > one note in parenthesis, too) > */ Your comment then becomes: /* This is just a C comment. Nothing fancy - it just has some general text (and perhaps one note in parenthesis, too) */ Ctext will obligingly put the whole thing in italics. I've gotten to almost love my ctext over the last year or more, since I made it use the Andy font set (variable pitch, serifs). Now if I could keep it from turning spaces into tabs early in the line when I hit the tab key. (Yes, I understand how TAB typed after four spaces wants to replace those four spaces with a tab character. I just don't want it to turn earlier spaces into tab characters too.) Craig
Richard.Draves@CS.CMU.EDU (05/30/90)
> Excerpts from internet.info-andrew: 29-May-90 Re: ctext suggestion Craig > F. Everhart (1052+0) > One way of doing comments in ctext is simply to type everything on one > line. I use it all the time and haven't yet found a C compiler that > complains about very long lines, all of which is a comment. And people who don't love ez/ctext will hate you. Rich
tpn+@ANDREW.CMU.EDU (Tom Neuendorffer) (05/30/90)
Excerpts from mail: 29-May-90 Re: ctext suggestion Craig F. Everhart (1052+0) > One way of doing comments in ctext is simply to type everything on one > line. I use it all the time and haven't yet found a C compiler that > complains about very long lines, all of which is a comment. The problem with this is that while long lines may not bother C compilers, they can bother tools like ed and diff, and can thus render other tools (like patch) useless. We had a problem here with trying to send out a patch to a file with a very long line, and finding that we just couldn't do it. I would recommend against this practice. Tom N.
tom@ICASE.EDU (Tom Crockett) (05/30/90)
Excerpts from internet.info-andrew: 29-May-90 Re: ctext suggestion Richard.Draves@cs.cmu.ed (352+0) >> Excerpts from internet.info-andrew: 29-May-90 Re: ctext suggestion Craig >> F. Everhart (1052+0) >> One way of doing comments in ctext is simply to type everything on one >> line. I use it all the time and haven't yet found a C compiler that >> complains about very long lines, all of which is a comment. > And people who don't love ez/ctext will hate you. Yes, e.g., vgrind/tgrind output is hard to read if your lines are too long! And sometimes I even write C code which has to be ported to machines which (gasp!) don't have Andrew available on them! Generally, though, I like ctext -- I use it all the time, even though I have to coerce and threaten it occasionally.