1: Piping curl into a pager (7) 2: Code Thread (22) 3: Perl6 'fun' (9) 4: Nikita (47) 5: Is Computer Science the most redpilled field? (11) 6: CloverOS GNU/Linux (68) 7: Small /proggles/ girl (58) 8: Donald Knuth appreciation thread (14) 9: Touhou Cirno Radio / chiru.no (229) 10: The Big Bang Theory (8) 11: /prog/ Challenge 63: House of Annus (33) 12: Hey (28) 13: 3D modeling (7) 14: Prog chaleng (6) 15: Provably undecidable problems (10) 16: Being Stalked by Filthy Gypsy (22) 17: Linux Users are Rude Thieves (122) 18: the state of web development (8) 19: funny memes (47) 20: No ANIME please (12) 21: Where did our people go? (39) 22: ATTN whoever got our company IP banned from tinychan (7) 23: Simple way to ensure null-safety (3) 24: /prog/ Challenge: HP Bar (11) 25: /prog/ API (9) 26: hax my aniii (4) 27: the fallacies of being cummed inside (4) 28: best programming language for EDC? (4) 29: ive decided i like free and open source software (39) 30: Object Oriented Nonsense (21) 31: Security protocols (8) 32: Consider this (10) 33: Banned for Nothing (49) 34: /prog/ Challenge: RFC 6503 (25) 35: Is this the house of spastics? (7) 36: Symta Brevity (8) 37: so Twitter mass banned "russian bots" (3) 38: /prog/ Challenge: JPEG9001 (15) 39: /prog/ Challenge: Micro$oft Excel 2018 (23) 40: Why is ios so good? (27)
>>12,13 Next in plan is creating a 'lshttp' script (similar to ls) for listing all linked hyperlinks inside a given web page. Something like #!/bin/bash curl $1 | sed '/<\s*a \s*href\s*=\s*"([^"])"/gi!d' (Haven't tested yet.)
Name:
Anonymous2018-02-27 14:35
>>17 this is going to be the worst, least convenient way to browse the internet
>>21 Curl is against my religion, I refuse to use it. I also feel offended that you use #!/bin/bash instead of #!/bin/sh.
Name:
Anonymous2018-02-27 23:04
>>26 Then substitute it for the world wide web application of your choice.
I also feel offended that you use #!/bin/bash instead of #!/bin/sh.
To be honest, I've started learning shell script recently, and haven't yet gathered enough experience to develop any sense of elitism between shells.
Name:
Anonymous2018-02-28 8:03
>>27 it's not about elitism, it's about portability. if your script works with #!/bin/sh, it will work with other Bourne-compatible shells (ash, dash, bash, probably ksh and zsh too but I'm not an expert on those)
>>23 First of all, you meant /<\s*a \s*href\s*=\s*"([^"]*)"/ second, that won't work if the tag has any other attribute before href. So it only works for basic html.
>>28 Makes sense. I'll start testing it with sh to check if it is portable. >>18 I'll pipe that output into something else later, but it is useful to have that as a separate tool.
Could this be used as the basis for a text-based browser?
I'm gonna save you the trouble, and tell you this isn't a good idea. Lots of people had the same idea before you, and it never amounted to anything. Just fork elinks and do what you want with that.
Is there actually any text browser that's still in development (at least recently)? Always thought it was odd how there aren't any still made. It's not like it's a real waste.
Name:
Anonymous2018-03-09 22:35
>>50 Why does it still need development when it's already complete?
But I was also wondering why people don't do this >>42. Lots of people would use a good terminal browser, so why is there no interest in creating/forking one?
And no, using elinks as-is is not ideal, as >>52-san says.
>>56 I've lookep up the possibility of doing this on Guile Scheme, and guile has a package with bindings for ncurses and also native support for most www operations.