9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mats Olsson <plan9.meo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Persistent font in Acme.
Date: Fri,  7 Nov 2014 20:53:09 +0000	[thread overview]
Message-ID: <CAEj9f0JxN6wWT=16HcQYt_rNp5oYL9oYwieqFqsuB9MmDBO4yQ@mail.gmail.com> (raw)
In-Reply-To: <CABJnqBSjCr4AkHbV36v0hNkN+O20rr9-ZaQYvgDBTW-VT6BghA@mail.gmail.com>

I like the idea of making a small script but I couldn't make it work.
What I want is to get this to execute without to much typing:
term%acme -f /lib/font/bit/lucidasans/latin1.10.font and that's it.
Any suggestion for a script and how to execute it would be most
appreciated.
Kind greetings,
Mats

2014-11-06 14:56 GMT, Iruatã Souza <iru.muzgo@gmail.com>:
> yes, but what about two fonts? I only remember acme.
>
> On Thu, Nov 6, 2014 at 12:37 PM, Lee Fallat <ircsurfer33@gmail.com> wrote:
>> On Thu, Nov 6, 2014 at 9:04 AM, Iruatã Souza <iru.muzgo@gmail.com> wrote:
>>> what other program needs two fonts?
>>>
>>> On Thu, Nov 6, 2014 at 11:30 AM, erik quanstrom <quanstro@quanstro.net>
>>> wrote:
>>>> On Thu Nov  6 08:15:54 EST 2014, iru.muzgo@gmail.com wrote:
>>>>> acme is not the system.
>>>>>
>>>>> On Thu, Nov 6, 2014 at 10:48 AM, Stuart Morrow
>>>>> <morrow.stuart@gmail.com> wrote:
>>>>> > The way most congruent with the system might be to have $font a
>>>>> > 2-variable (like prompt), to have you favourite fixed- and
>>>>> > variable-width fonts both settable in the obvious place: your
>>>>> > profile.
>>>>> > Completely unrelated programs could conceivably reuse this trick.
>>>>
>> https://code.google.com/p/plan9front/source/browse/sys/src/cmd/rio/rio.c#173
>>
>> rio uses what is in $font if not specified on the command-line.
>>
>> You can easily implement it in any gui in plan 9.
>>
>
>



  reply	other threads:[~2014-11-07 20:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 10:01 Mats Olsson
2014-11-06 10:07 ` dante
2014-11-06 10:13 ` Ingo Krabbe
2014-11-06 12:48   ` Stuart Morrow
2014-11-06 13:14     ` Iruatã Souza
2014-11-06 13:30       ` erik quanstrom
2014-11-06 14:04         ` Iruatã Souza
2014-11-06 14:37           ` Lee Fallat
2014-11-06 14:56             ` Iruatã Souza
2014-11-07 20:53               ` Mats Olsson [this message]
2014-11-06 10:13 ` Mark van Atten
2014-11-07 20:03 sl
2014-11-07 22:13 ` Mats Olsson
2014-11-08  7:18   ` erik quanstrom
2014-11-08  8:29     ` Mats Olsson
2014-11-08  9:42     ` Richard Miller
2014-11-08 10:35       ` Mats Olsson
2014-11-08 13:47         ` Richard Miller
2014-11-08 14:17           ` Mats Olsson
2014-11-08 11:06       ` cinap_lenrek
2014-11-09  2:16       ` erik quanstrom
2014-11-09  9:46         ` Richard Miller
2014-11-08 15:02     ` Anthony Sorace
2014-11-09  2:06       ` erik quanstrom
2014-11-07 21:22 sl
2014-11-07 22:34 ` Mats Olsson

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='CAEj9f0JxN6wWT=16HcQYt_rNp5oYL9oYwieqFqsuB9MmDBO4yQ@mail.gmail.com' \
    --to=plan9.meo@gmail.com \
    --cc=9fans@9fans.net \
    /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).