From: "James A. Robinson" <jim.robinson@stanford.edu>
To: "sam Fans" <sam-fans@hawkwind.utcs.toronto.edu>
Subject: the obvious. =)
Date: Fri, 24 Mar 2000 16:25:07 -0500 [thread overview]
Message-ID: <200003242125.NAA22426@highwire.stanford.edu> (raw)
I just have to shout to the world (well, to sam fans) that this editor
is wonderful! Now that I'm actually working directly in sam instead of
just using it via a pipe (from wily), I'm amazed at how much easier it
is to do stuff.
One of the things I tend to do in Java is write a method with name X
that takes no args, X(), or takes N args, X(N). X() tends to just pass
some sort of defaults on to X(N).
When writing JavaDoc comments for each method, it's a major pain
a lot of it tends to be a straight copy and paste one to the
other
Now, with sam, I can just write the top java doc comment, and when
I'm finally ready I can just write
,x/^\/\*(.+\n)+ \*\/\n/ t /}\n/
To copy the top comment down to the second method. e.g.
/**
* 1-5 lines describing Foo
*/
public void X()
{
...
}
public void X(N)
{
...
}
turns into
/**
* 1-5 lines describing Foo
*/
public void X()
{
...
}
/**
* 1-5 lines describing Foo
*/
public void X(N)
{
...
}
sam's slogan ought to be 'Making your life easier through
structured regular expressions.' =)
Jim
next reply other threads:[~2000-03-25 6:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-24 21:25 James A. Robinson [this message]
2000-03-25 23:47 kim kubik
2000-03-26 1:51 ` James A. Robinson
[not found] <chaotrope@jps.net>
2000-03-26 20:54 ` kim kubik
2000-03-27 3:35 ` James A. Robinson
2000-03-27 14:37 rob pike
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=200003242125.NAA22426@highwire.stanford.edu \
--to=jim.robinson@stanford.edu \
--cc=sam-fans@hawkwind.utcs.toronto.edu \
/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 NNTP newsgroup(s).