From: khi at users.sourceforge.jp (khi at users.sourceforge.jp)
Subject: [Howm-eng 80] Re: Effective use of <<< or >>> ?
Date: Mon, 21 Apr 2008 21:45:09 +0900 [thread overview]
Message-ID: <m34p9vz8a2.wl@id.domain> (raw)
In-Reply-To: <200804152203.m3FM3pVU004987@localhost.localdomain>
Hi.
At Wed, 16 Apr 2008 00:03:51 +0200,
Xavier Maillard wrote:
> It is not really clear how one should use the goto and come-from
> links. How are you all doing ? Is it prefered to use them as much
> as possible or not ?
I also want to hear it. :-)
In my experience, these are convenient for come-from keywords.
- names of machines
- names of softwares/commands
- names of authors of interesting books/papers
- names of lectures
I cannot show a good general guide because I'm lazy, loose, and bad at
tidying. I've already given up well-ordered notes. Howm may be
suitable for those who are tired from strict systems.
--
khi at users.sourceforge.jp
next prev parent reply other threads:[~2008-04-21 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 22:03 [Howm-eng 78] " xma
2008-04-21 12:45 ` khi [this message]
2008-04-22 19:49 ` [Howm-eng 81] " xma
2008-04-22 20:57 ` [Howm-eng 82] " hugows
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=m34p9vz8a2.wl@id.domain \
--to=howm-eng@lists.osdn.me \
/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).