9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Kenji Okamoto <okamoto@granite.cias.osakafu-u.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] links bug
Date: Fri, 23 Jul 2004 18:47:05 +0900	[thread overview]
Message-ID: <3526d4bc8156573db1beea212500628d@granite.cias.osakafu-u.ac.jp> (raw)
In-Reply-To: <98eba27c67917eb14a8d23b7378b3f0b@plan9.escet.urjc.es>

> I have been playing a little bit with links and got it working for us with
> varfont. The problems seems to be with (old code is commented).

Since Andrey said varfont version of links has some problem, I wondered
what is the problem....     I'm running here the varfont version, and I'm having
no problem (at least looks like so to me).   What is the real problem here...

Kenji



  reply	other threads:[~2004-07-23  9:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22  8:09 Gorka Guardiola Múzquiz
2004-07-23  9:47 ` Kenji Okamoto [this message]
2004-07-23 10:11   ` Kenji Okamoto
2004-07-23 11:12     ` Gorka Guardiola Múzquiz
2004-07-26  2:19       ` Kenji Okamoto
2004-07-23 14:46   ` andrey mirtchovski

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=3526d4bc8156573db1beea212500628d@granite.cias.osakafu-u.ac.jp \
    --to=okamoto@granite.cias.osakafu-u.ac.jp \
    --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).