all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: indieterminacy <indieterminacy@libre.brussels>
To: Christopher Howard <christopher@librehacker.com>
Cc: Felix Lechner <felix.lechner@lease-up.com>,
	Steve George <steve@futurile.net>,
	guix-devel@gnu.org
Subject: Re: Please take the User and Contributor survey
Date: Tue, 12 Nov 2024 16:26:43 +0000	[thread overview]
Message-ID: <e82cbe256ae1484d3e4f671fae6a865f@libre.brussels> (raw)
In-Reply-To: <8734jwsd9p.fsf@librehacker.com>

Hello Christopher,

On 2024-11-12 15:05, Christopher Howard wrote:
> Thank you, Felix. I can't view all of the questions without the 
> JavaScript, but if Steve or Felix could just copy and paste the 
> questions once into plain text, that would work.

I would mention experimenting with Elinks (I believe the Felinks fork 
was merged again upstream),
as it has both TUI functionality and some utility regarding simpler 
Javascript:
https://github.com/rkd77/elinks

However, the recommendation is with caution, given it appears to not be 
in our common package definitions.
This may have been about historical concerns about bitrot and 
maintainability (it was dormant for some time) but I dont have the time 
to form a contemporary evaluation.

HTH,


Jonathan


  parent reply	other threads:[~2024-11-12 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 15:05 Please take the User and Contributor survey Christopher Howard
2024-11-12 15:57 ` Steve George
2024-11-12 16:26 ` indieterminacy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-11 22:11 Christopher Howard
2024-11-12  9:23 ` Steve George
2024-11-12 10:31   ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-11-12 15:33 ` Luis Felipe
2024-11-12 19:44   ` Christopher Howard
2024-11-11 10:30 Steve George

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=e82cbe256ae1484d3e4f671fae6a865f@libre.brussels \
    --to=indieterminacy@libre.brussels \
    --cc=christopher@librehacker.com \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --cc=steve@futurile.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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.