Xref: utzoo comp.emacs:10794 comp.editors:3259 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbfsb!danj1 From: Dan_Jacobson@ATT.COM Newsgroups: comp.emacs,comp.editors Subject: line number nonimportance Message-ID: <1991May30.155147.3985@cbfsb.att.com> Date: 30 May 91 15:51:47 GMT References: <1991May30.124131.4679@bronze.ucs.indiana.edu> Sender: news@cbfsb.att.com Reply-To: Dan_Jacobson@ihlpz.ATT.COM Organization: AT&T-BL, Naperville IL, USA Lines: 39 In-Reply-To: bob@MorningStar.Com's message of 30 May 91 13: 46:12 GMT Originator: danj1@cbnewsf.cb.att.com >>>>> On 30 May 91 13:46:12 GMT, bob@MorningStar.Com (Bob Sutterfield) said: In article <1991May30.124131.4679@bronze.ucs.indiana.edu> ury@mosque.huji.ac.il (ury segal) writes: >(By the way, How you get the current line number ?) Bob> You didn't mention what version of Emacs you were trying to use, so Bob> I'll answer from the perspective of a GNU Emacs user. I said "M-x Bob> apropos line", searched the resulting *Help* buffer for the string Bob> "number", and quickly found Bob> what-line Bob> Function: Print the current line number (in the buffer) of point. Bob> 2) I only need to use what-line and friends on very, very rare Bob> occasions, like once in every two or three months of quite heavy Bob> Emacs use for a variety of tasks. In fact, I didn't remember Bob> (what-line) from the last time I used it, so I actually needed to Bob> look it up, as described above, to answer your question. I find it Bob> curious that you needed it within the first few hours of beginning Bob> to use the editor. Your working style must be quite different from Bob> mine. Bob fails to mention the key to why a GNU Emacs user wouldn't bother with line numbers anymore than one keeps track of highway mile-marker numbers on a trip from Memphis to Philadelphia. It would be unfair not to explain this further. Here are some of Bob's secrets, available via ESCAPE x compile: Compile the program including the current buffer. Default: run `make'. Runs COMMAND, a shell command, in a separate process asynchronously with output going to the buffer *compilation*. You can then use the command C-x ` to find the next error message and move to the source code that caused it. grep: Run grep, with user-specified args, and collect output in a buffer. While grep runs asynchronously, you can use the C-x ` command to find the text that grep hits refer to.