All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ragnar Hojland Espinosa <ragnar@linalco.com>
To: "Kerl, John" <John.Kerl@Avnet.com>
Cc: "'David Weeks'" <dweeks02@tampabay.rr.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Twister chipset... other stuff...  sheesh...
Date: Sat, 29 Jun 2002 21:43:13 +0200	[thread overview]
Message-ID: <20020629194313.GA28230@linalco.com> (raw)
In-Reply-To: <C08678384BE7D311B4D70004ACA371050B763539@amer22.avnet.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 885 bytes --]

On Fri, Jun 28, 2002 at 06:15:17PM -0700, Kerl, John wrote:
> is 42 MB (ctags -R) vs. 13 MB (make tags).
> 
> Also, you shouldn't (TM) have to search the tags
> file yourself.  Emacs & vi & vim have commands such
> as "show me the file this symbol is in", with just
> a few keystrokes, and the editor will do the grunt
> work of searching the tags file for you, as well as
> getting you back where you came from ("tag stack").
> All you have to do is tell the editor where the tags
> file is. (Sorry to be vague on *how*, but I'm a vim

Also see man ref(1) and less -t for everyday tools.
-- 
____/|  Ragnar Højland      Freedom - Linux - OpenGL |    Brainbench MVP
\ o.O|  PGP94C4B2F0D27DE025BE2302C104B78C56 B72F0822 | for Unix Programming
 =(_)=  "Thou shalt not follow the NULL pointer for  | (www.brainbench.com)
   U     chaos and madness await thee at its end."            CCNA

  reply	other threads:[~2002-06-29 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-29  1:15 Twister chipset... other stuff... sheesh Kerl, John
2002-06-29 19:43 ` Ragnar Hojland Espinosa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-29  0:34 David Weeks

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=20020629194313.GA28230@linalco.com \
    --to=ragnar@linalco.com \
    --cc=John.Kerl@Avnet.com \
    --cc=dweeks02@tampabay.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.