From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: about acme!
Date: Mon, 23 Apr 2007 08:46:03 +0000 [thread overview]
Message-ID: <jNednav0KddcAbTbnZ2dnUVZ_hynnZ2d@comcast.com> (raw)
In-Reply-To: <1177044636.872917.296280@b58g2000hsg.googlegroups.com>
"sameer" <sameersmail@gmail.com> wrote...
> how can i make acme or sam to tell me which line of text my cursor is
> at
> or maybe how could i jump to a particular line number of text in
> either of the editors
In the sam command window, .= will print the current value of dot
(cursor location or highlighted character sequence). including the
line number. And typing in a line number (then newline) will move
dot to that line.
next prev parent reply other threads:[~2007-04-23 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 8:54 [9fans] " sameer
2007-04-20 9:03 ` Christian Kellermann
2007-04-20 9:57 ` matt
2007-04-20 11:57 ` sameer gupta
2007-04-21 6:55 ` Markus Maria Miedaner
2007-04-22 7:12 ` sameer gupta
2007-04-23 8:46 ` Douglas A. Gwyn [this message]
2007-04-24 6:16 ` [9fans] " cej
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=jNednav0KddcAbTbnZ2dnUVZ_hynnZ2d@comcast.com \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.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).