about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAge
* Fix makefileCase Duckworth2020-06-07
|
* Add commentsCase Duckworth2020-06-07
|
* Update manpageCase Duckworth2020-06-07
|
* Change display and keymapsCase Duckworth2020-06-07
|
* Comment unused optionsCase Duckworth2020-06-07
|
* Change less optionsCase Duckworth2020-06-07
|
* Support status code 11Case Duckworth2020-06-07
|
* Update READMECase Duckworth2020-06-07
|
* Update READMECase Duckworth2020-06-07
|
* Update documentationCase Duckworth2020-06-07
|
* Set timeoutCase Duckworth2020-06-07
|
* Add gophertypes 7 and hopefully others (download)Case Duckworth2020-06-04
|
* Add gopher support; clean upCase Duckworth2020-06-04
|
* Version bumpCase Duckworth2020-06-03
|
* Update docsCase Duckworth2020-06-03
|
* Add G bindCase Duckworth2020-06-03
|
* Add back/forward binds to statuslineCase Duckworth2020-06-02
|
* Fix title extractionCase Duckworth2020-06-02
|
* Change variables and update manpagesCase Duckworth2020-06-02
|
* Customize Bye MessageCase Duckworth2020-06-02
|
* Change ssl_cmd settingCase Duckworth2020-06-02
|
* Added explicit support for TLS v1.3Parker Ellertson2020-06-02
| | | | | | | From 8d20bf3b790991a33c0ab721a2746ec222a74f2a Mon Sep 17 00:00:00 2001 From: Parker Ellertson <pellertson@firemail.cc> Date: Tue, 2 Jun 2020 15:06:34 -0700 Subject: [PATCH bollux] Added explicit support for TLS v1.3
* Add wipCase Duckworth2020-06-02
| | | | | This is where all my works in progress are going to go. Expect it to be really messy.
* Add history fileCase Duckworth2020-06-02
| | | | | | | | | | | | I added a history file at $XDG_DATA_HOME/bollux/history. Its format is of the form <date %FT%T> <URL> <TITLE> the date is generated with the printf trick. I should probably be doing version checking or at least say we require bash 4+. The code to get the title of the page is pretty gross. Basically I have to run the content of the pipeline through like, two times? A read loop. Check out ll. 333-348 to see how weird it is.
* Reimplement extract_links in bashCase Duckworth2020-06-02
|
* Remove iconv dashCase Duckworth2020-06-02
|
* Merge branch 'master' into historyCase Duckworth2020-06-01
|\
| * Add keybindCase Duckworth2020-06-01
| |
| * Add INSTALL sectionCase Duckworth2020-06-01
| |
| * update READMECase Duckworth2020-06-01
| |
* | Fix beginning of history detectionCase Duckworth2020-06-01
| |
* | Add rudimentary history support.Case Duckworth2020-06-01
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds `history_init`, `history_append`, `history_back`, and `history_forward` functions. The history is implemented as an array, HISTORY, which is appended to with history_append when pages are visited, and a pointer, HN, which points to the current position in the array. When history_back is called, it moves the pointer back 2 and calls blastoff to the URL there. When history_forward is called, it does not move the pointer and blastsoff to the URL. Why back and forward basically have an off-by-one error is beyond me at this time. ISSUES: - if the user goes back then forward, the history is not rewritten for later URLs. for example, if the history is 1.gmi 2.gmi 3.gmi* where the * indicates the current history position, when the user goes back 2, it looks like this: 1.gmi* 2.gmi 3.gmi if the user then navigates to another page: 1.gmi 4.gmi* 3.gmi 3.gmi is still in the history, so the user can go forward from 4. This is unexpected as far as every other client that I know of goes.
* Accept but ignore pre lines with alt textCase Duckworth2020-06-01
|
* Add quit message and set titleCase Duckworth2020-05-31
|
* Trim mime and only look at it onceCase Duckworth2020-05-31
|
* Handle different charsetsCase Duckworth2020-05-31
|
* Change config and args orderCase Duckworth2020-05-31
|
* Log, don't echoCase Duckworth2020-05-31
|
* Version bumpCase Duckworth2020-05-31
|
* Fix config file locationCase Duckworth2020-05-31
|
* Fix line endingsCase Duckworth2020-05-30
|
* Version bumpCase Duckworth2020-05-30
|
* Remove port number from parsed authorityCase Duckworth2020-05-30
| | | | | | | | | When navigating to a link with the port included, request_url doesn't do the right thing. For now I've changed the code in transform_resource to remove the port from the authority field, but that is probably not the right place to put it. I'm going to deal with this later though.
* Update docsCase Duckworth2020-05-30
|
* Change margin stuffCase Duckworth2020-05-30
|
* Update typesetting of text/geminiCase Duckworth2020-05-30
|
* ArchiveCase Duckworth2020-05-30
|
* Change some functions to only BashCase Duckworth2020-05-30
|
* Remove unneeded filesCase Duckworth2020-05-30
|
* Bring URL transforming up to specCase Duckworth2020-05-30
| | | | | | URL transformation (formerly called "munging") is now (afaict) fully compliant with the RFC spec. It's also implemented in pure bash and is available as a library at https://git.sr.ht/~acdw/shurlie.
© 2022 C. Duckworth. generated by cgit. comments, issues, and patches welcome at < git at acdw dot net >.