antes de preguntarle al agente, todavía prefiero primero preguntarle a la gente
Nico
@nsanmartin
- 9 Followers
- 65 Following
- 18 Posts
According to this thread, using [static 1] for a parameter is not to check that it is not null, but instead an optimization hint. If a null pointer is passed you have undefined behavior, so it is worse if you cannot guarantee.
It would be nice using [1] could have that meaning, I don't know if there is any reason arrays must decay to pointers though.
... so since I haven't implemented the javascript needed to search in google in ahre, I opted to first add a flag to pass key=values to make a post request from the cli https://codeberg.org/nsm/ahre/pulls/33
Most of quick searches I usually do can be done with a text browser, or at least could. For some time, google required javascript but made an exception for user-agent (I don't remember if w3m or Elinks), but not anymore. So I stated using duckduckgo. But I had a script that made all in one step (pass the query to it and it shows the search) and since the duckduckgo search is a post method, you cannot just launch the browser opening the search with the query (at least the browsers I was using)...
Andrew Kelleycan't believe it's 2025 and people are programming in memory unsafe languages like Rust and Go when Fil-C exists
RE: https://mastodon.social/@nsanmartin/114570776910561677
I was using w3m as user agent in order to use google searchs, but it does not make the exception any more, now all browsers are required to support javascript. I may use duckduckgo/lite or bing. But I'd prefer a search engine based only on regex.
I'm writing a text-based web navigator based on libcurl and lexbor (next step would be adding DOM bindings to quickjs I suppose) and I'm finding it useful for my own use of the internet.
Since there are so many things to be done maybe some edbrowse or w3m users are willing to provide some feedback on what could be prioritized or which features should be implemented (although the idea is not to implement all the features browsers need)
ahora Google quiere que usemos Javascript para hacer búsquedas https://news.ycombinator.com/item?id=42719865
Cambió el mantainer de w3m y ahora el proyecto está en sourcehut. Ya no va a depender de otros browsers como chrome o firefox