From: Jean Louis <bugs@gnu.support>
To: Yuchen Pei <id@ypei.org>
Cc: Emacs Devel mailing list <emacs-devel@gnu.org>
Subject: Re: [ELPA] New package: luwak
Date: Fri, 21 Oct 2022 10:03:29 +0300 [thread overview]
Message-ID: <Y1JEQdq4EPWm6myi@protected.localdomain> (raw)
In-Reply-To: <871qr196ya.fsf@ypei.org>
* Yuchen Pei <id@ypei.org> [2022-10-21 06:50]:
> On Fri 2022-10-21 06:26:51 +0300, Jean Louis wrote:
>
> > Lynx without Emacs works fine, and luwak can't get the page as it
> > tries using torsocks automatically:
>
> Thanks for trying it out.
>
> Now I think of it, perhaps it makes more sense for the tor-switch should
> be the other around. I have pushed a commit to toggle the default value
> of luwak-tor-switch.
>
> >
> > 1666322739 PERROR torsocks[21360]: socks5 libc connect: Connection
> > refused (in socks5_connect() at socks5.c:202)
>
> This looks like tor is not on. Are you able to get output from say
>
> torsocks wget -qO- https://check.torproject.org/ | grep -i congratulations
Because Tor is not started:
$ torsocks wget -qO- https://check.torproject.org/ | grep -i congratulations
1666335386 PERROR torsocks[30029]: socks5 libc connect: Connection refused (in socks5_connect() at socks5.c:202)
I do not think that package that is supposed to provide browsing shall
supposedly automate activation of Tor. That shall be optional. It
needs instructions for user to understand that it requires Tor, but
why it should require it? There is no reason for it. Using Tor is
generally useful, but there is no reason for browsing package to
require it.
After:
$ sudo rc-service tor start
* /run/tor: creating directory
* /run/tor: correcting owner
* Starting tor ...
$ torsocks wget -qO- https://check.torproject.org/ | grep -i congratulations
Congratulations. This browser is configured to use Tor.
Congratulations. This browser is configured to use Tor.
If you only say that `torsocks' is to activate it all, then there is
problem, as Tor does not run in background.
Think of usability of the package for browsing.
Further, it seems I can't access any of the links:
error in process sentinel: save-excursion: Args out of range: #<buffer *luwak*>, 0, 70
error in process sentinel: Args out of range: #<buffer *luwak*>, 0, 70
Further, I think that numbered links shall be activated by using
numbers: 12 RET to activate link number 12.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-10-21 7:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 1:05 [ELPA] New package: luwak Yuchen Pei
2022-10-21 3:26 ` Jean Louis
2022-10-21 3:44 ` Yuchen Pei
2022-10-21 7:03 ` Jean Louis [this message]
2022-10-21 9:53 ` Yuchen Pei
2022-10-21 10:54 ` Jean Louis
2022-10-21 12:50 ` Yuchen Pei
2022-10-21 10:55 ` Jean Louis
2022-10-21 12:51 ` Yuchen Pei
2022-10-25 19:09 ` Stefan Monnier
2022-10-26 1:53 ` T.V Raman
2022-10-26 5:52 ` Stefan Kangas
2022-10-30 11:16 ` Yuchen Pei
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y1JEQdq4EPWm6myi@protected.localdomain \
--to=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=id@ypei.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).