From: Steve Simon <steve@quintile.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] osc drawterm big sur
Date: Thu, 19 Nov 2020 11:40:00 +0000 [thread overview]
Message-ID: <E6F64D1E-4097-41AB-934C-B6FAA5BDF80A@quintile.net> (raw)
In-Reply-To: <1B403B39-D043-4A34-952B-96C99A582E06@me.com>
i just have the xcode supplied clang and it works well.
i have two issues with it:
my shift key is generating spurious peter-face characters which makes typing rather painful (i have to delete these as i type)
there is no /mnt/term/dev/secstore device containing my secstore when i authenticated to drawterm, so i need to authenticate to secstore again in my profile which is irritating. this may be by design as having drawterm know. all my secrets feels a bit foolish.
it idefinitely feels much snappier than the old drawterm.
thanks
-Steve
> On 19 Nov 2020, at 11:25 am, Daniel Morandini via 9fans <9fans@9fans.net> wrote:
>
> Hi folks,
>> While I don't have Big Sur, the drawterm at
>> http://drawterm.9front.org/ builds fine for
>> me with cocoa + catalina:
>>
>> cd $drawterm
>> mk CONF=osx-cocoa
>>
>> You need all of xcode installed to process
>> some of the interface builder files.
>>
>> If there are issues on big sur, let me know.
> I just double checked on Big Sur and works as stated above,
> ** provided CC=clang ** [1]
>
> Does not work with gcc.
>
> dan
>
> [1] Apple clang version 12.0.0 (clang-1200.0.32.2)
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T8287ca5a12c53519-M2be4564f39a535729223dbb4
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2020-11-19 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 13:17 Steve Simon
2020-11-18 13:54 ` Michael Engel
2020-11-18 16:37 ` ori
2020-11-19 11:25 ` Daniel Morandini via 9fans
2020-11-19 11:40 ` Steve Simon [this message]
2020-11-19 14:58 ` sirjofri
2020-11-20 10:30 ` Steve Simon
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=E6F64D1E-4097-41AB-934C-B6FAA5BDF80A@quintile.net \
--to=steve@quintile.net \
--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).