Hi,
Sorry for taking so long to chime in.
On Wed, 19 Dec 2018 22:32:22 +0100
Pierre Neidhardt wrote:
> [...]
>
> That would not be consistent with the Lisp library naming scheme then.
> And it raises the question as to why we have bothered with the sbcl-
> and ecl- prefixes so far.
>
> Andy,
Ricardo Wurmus writes:
> The naming scheme applies to packages that are primarily used as
> libraries. A package “foo” that is written in Python and also provides
> modules that can be imported in an interactive Python session will not
> be named “python-foo” when it is primarily used on its
Pierre Neidhardt writes:
> Brett Gilio writes:
>> Excuse me for not being fully aware, are you involved in the development
>> of the Next browser?
>
> I am! John Mercouris is the original author, and I've implemented the
> WebKitGTK
> platform for Next.
>
Is there a mailing list for this,
Pierre Neidhardt writes:
> - As far as I understand, the compiler *does* change the resulting
> binary, thus the resulting REPL experience will be different, because
> all Lisps are different beyond the ANSI standard and other undefined
> behaviour. In other words, connecting via SLIME to
Brett Gilio writes:
> Excuse me for not being fully aware, are you involved in the development
> of the Next browser?
I am! John Mercouris is the original author, and I've implemented the WebKitGTK
platform for Next.
Ricardo Wurmus writes:
> I’ve read that discussion, but I don’t see how it
Hi Pierre,
>> I am also in favor
>> of renaming SBCL-Next to something else. I know that we are using sbcl
>> instead of clisp for building it, but the naming scheme seems to imply
>> an SBCL library or module rather than a web browser application.
>
> This is being discussed for stumpwm in bug
Ricardo Wurmus writes:
> Hi Pierre,
>
>>> I am also in favor
>>> of renaming SBCL-Next to something else. I know that we are using sbcl
>>> instead of clisp for building it, but the naming scheme seems to imply
>>> an SBCL library or module rather than a web browser application.
>>
>> This is
Pierre Neidhardt writes:
>> Hi all, I am also using the Next browser. A terrific tool.
>
> Oh, and I forgot: Thanks for the compliment! :)
Excuse me for not being fully aware, are you involved in the development
of the Next browser? I have been following it for some time, and am
genuinely
Ludovic Courtès writes:
> Hello!
>
> Pierre Neidhardt skribis:
>
>> I'm happy to let you know that after months of feisty packaging and the
>> last month spent on the full rewrite of the GNU/Linux port, the Next web
>> browser is finally on master!
>>
>> It's packaged as sbcl-next.
>
> Before
> That’s because ‘guix size’ disables grafts, which allows it to check the
> size of substitutes (build farms provide substitutes for ungrafted
> variants.)
> Before reading your message I naively installed ‘next-webkit-gtk’, which
> is not supposed to be used directly, right? Should we make it
Pierre Neidhardt skribis:
> Forget the above, I was wrong. "guix pack" works well with regard to finding
> the correct executable, with or without graft (could be wrong again, but so
> far
> it seems to work).
>
> The issue is that "next" cannot send XML-RPC requests to "next-gtk-webkit".
>
Pierre Neidhardt skribis:
> Hmm, I'm having an issue with Guix pack.
>
> Check out the following:
>
> $ ./pre-inst-env guix build next-gtk-webkit
> /gnu/store/ildn4l2wr0y7irm2536dnp88hhrdphsz-next-gtk-webkit-1.1.0
>
> $ ./pre-inst-env guix size next-gtk-webkit
> store item
Hello!
Pierre Neidhardt skribis:
> I'm happy to let you know that after months of feisty packaging and the
> last month spent on the full rewrite of the GNU/Linux port, the Next web
> browser is finally on master!
>
> It's packaged as sbcl-next.
Before reading your message I naively installed
On 2018-12-11 08:46, Pierre Neidhardt wrote:
> Hi! Thanks for the feedback.
>
>> M-x
>> scroll the list to the bottom (with down-arrow) (freezez at
>> JUMP-TO-HEADING)
>
> I can't reproduce this. Can you produce this systematically? Can you post
> the
> content of /tmp/next-gtk-webkit.log?
Hi! Thanks for the feedback.
> M-x
> scroll the list to the bottom (with down-arrow) (freezez at
> JUMP-TO-HEADING)
I can't reproduce this. Can you produce this systematically? Can you post the
content of /tmp/next-gtk-webkit.log?
> “next-gtk-webkit” is not responding."
Where do you see
On 2018-12-05 11:34, Pierre Neidhardt wrote:
snip
> It's still rather alpha and some features are missing (such as cookie
> support), but rest assured it won't take long!
>
> As always, feedback is more than welcome!
I tried it out for some time now. Unfortunately it is buggy and freezes
on me
Actually, here is a clue:
> ./pre-inst-env guix build --check next-gtk-webkit
The following graft will be made:
/gnu/store/jgb5j3pg45kf19n7cgw1j5kjagzmbqg1-next-gtk-webkit-1.1.0.drv
applying 2 grafts for
/gnu/store/jgb5j3pg45kf19n7cgw1j5kjagzmbqg1-next-gtk-webkit-1.1.0.drv...
grafting
Hmm, I'm having an issue with Guix pack.
Check out the following:
--8<---cut here---start->8---
$ ./pre-inst-env guix build next-gtk-webkit
/gnu/store/ildn4l2wr0y7irm2536dnp88hhrdphsz-next-gtk-webkit-1.1.0
$ ./pre-inst-env guix size next-gtk-webkit
store item
On Thu, Dec 06, 2018 at 03:03:07PM +0100, Pierre Neidhardt wrote:
> > I cannot run ./bin/next, as it is looking for /gnu/store/...
> Do you have the full backtrace?
Unhandled SIMPLE-ERROR in thread #:
Couldn't execute
> I cannot run ./bin/next, as it is looking for /gnu/store/...
Do you have the full backtrace?
I know there is an issue at the moment, it's looking for the wrong
/gnu/store/...-next-gtk-webkit. I'm not sure what's wrong, I'll look into it.
> How do I change / to be .?
Documentation is being
On Thu, Dec 06, 2018 at 09:31:45AM +0100, Pierre Neidhardt wrote:
> > It seems to be the first ever? software project distributed reproducibly
> > with guix pack :)
> Indeed, haha! :) Still having issues with it though, hopefully I'll fix it
> later today. Otherwise I'll ask for more help here
> It seems to be the first ever? software project distributed reproducibly
> with guix pack :)
Indeed, haha! :) Still having issues with it though, hopefully I'll fix it
later today. Otherwise I'll ask for more help here ;)
--
Pierre Neidhardt
https://ambrevar.xyz/
signature.asc
On 2018-12-05 11:34, Pierre Neidhardt wrote:
> Hi Guix!
>
> I'm happy to let you know that after months of feisty packaging and the
> last month spent on the full rewrite of the GNU/Linux port, the Next web
> browser is finally on master!
>
> It's packaged as sbcl-next.
>
> Next is a web
Hi Ben,
Thanks for the praise!
I've already made it my default browser, so it's that usable at least!
More good stuff is coming, off the top of my head:
- VI-style bindings
- cookies
- status bar
- proxy settings (and more WebKit related options)
- Extended minibuffer (think Helm or Ivy!)
- A
Pierre,
This is great news! Just installed it via Guix and played with it for a
minute or two and am looking forward to more extensive use.
cheers,
-Ben
--
Benjamin Slade - https://babbagefiles.xyz
`(pgp_fp: ,(21BA 2AE1 28F6 DF36 110A 0E9C A320 BBE8 2B52 EE19))
'(sent by mu4e on Emacs
Hi Guix!
I'm happy to let you know that after months of feisty packaging and the
last month spent on the full rewrite of the GNU/Linux port, the Next web
browser is finally on master!
It's packaged as sbcl-next.
Next is a web browser written in Common Lisp, designed after Emacs: one
of its
26 matches
Mail list logo
