| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
default-flags was overly complicated for its purpose.
Also, ignore-case is quite useful, so enable it by default.
|
| |
|
|
|
|
|
|
|
| |
I've gotten tired of not being able to search for forward slashes.
Now it works like in vim, and you can also set default ignore case in
the config.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Until now, the config file required manual adjustment for the output to
look bearable on terminals colored differently than {bgcolor: black,
fgcolor: white}. Also, it only detected RGB when COLORTERM was set, but
this is not done by most (any?) terminal emulators (sad).
To improve upon the situation, we now query the terminal for some
attributes on startup:
* OSC(10/11, ?) -> get the terminal's bg/fgcolor
* DCS(+, q, 524742) -> XTGETTCAP for the "RGB" capability (only
supported by a few terminals, but better than nothing)
* Primary device attributes -> check if ANSI colors are supported, also
make sure we don't block indefinitely even if the previous queries
fail
If primary device attributes does not return anything, we hang until
the user types something, then notify the user that something went
wrong, and tell them how to fix it. Seems like an OK fallback.
(The DA1 idea comes from notcurses; since this is implemented by pretty
much every terminal emulator, we don't have to rely on slow timing hacks
to skip non-supported queries.)
|
|
|
|
| |
a bit more readable, and it also works with /[0-9]+ pathnames
|
|
|
|
| |
useful for filtering stuff through commands like rdrview
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* pass 0 so e.g. git does not hang
* use sigtstp so e.g. cgi scripts can clean up if needed
|
|
|
|
| |
This configuration scheme really is a nightmare to use :(
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Add functions for moving to the beginning/end of words (vi `b', `e').
* As it turns out, there are many possible interpretations of what a
word is. Now we have a function for each reasonable interpretation,
and the default settings match those of vi (and w3m in w3m.toml).
(Exception: it's still broken on line boundaries... TODO)
* Remove `bounds` from lineedit, it was horrible API design and mostly
useless. In the future, an API similar to what pager now has could
be added.
* Update docs, and fix some spacing issues with symbols in the tables.
|
|
|
|
|
|
| |
Now it actually does what it was supposed to do.
Also, clarify what it does in config.md
|
|
|
|
| |
hopefully this works
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
* Paths are now parsed through an unified code path with some useful
additions like environment variable substitution.
* Fix a bug in parseConfigValue where strings would be appended to
existing arrays (and not override them).
* Fix beforeLast calling afterLast for some reason.
* Add a default CGI directory.
|
|
|
|
|
| |
Default is vi-style, but w3m-style marks work as well; see
bonus/w3m.toml.
|
|
|
|
|
|
|
|
| |
{ & } acts like in vi (except the cursor is not moved to the line
beginning).
No reason to leave externInto undocumented, as it is even used in
the default config.
|
|
|
|
|
|
|
|
|
|
|
| |
Without this, setting color-mode using -o required quoting
the values, and then shell-quoting the quotes themselves
(cha -o 'display-color-mode="24bit"').
Instead of more special casing in the TOML parser, we just add aliases
for these enum values that can be parsed using TOML bare string
rules. So now this works:
cha -o display.color-mode=true-color
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Add w3m-style local CGI support.
It is not quite as powerful as w3m's local CGI, because it lacks an
equivalent to W3m-control. Not sure if it's worth adding; we certainly
shouldn't allow passing JS in headers, but a custom language for
headers does not sound like a great idea either...
eh, idk. also, TODO add multipart
|
| |
|
| |
|
| |
|
|
|
|
| |
8-bit colors are now supported
|
| |
|
|
|
|
|
|
| |
pandoc can only generate manpage tables from markdown tables, but the
markdown pipe table syntax is horrible. So instead of rewriting our markdown
documentation to use that syntax, just programmatically rewrite it.
|
|
|
|
| |
still needs some work
|
|
|
|
| |
it's better than nothing, maybe?
|
|
|
|
|
|
| |
These functions now take a numeric argument to determine how many
cells/lines to move. Also, update the default config so e.g. 9j
now works.
|
|
|
|
|
|
|
|
| |
* it is now possible to jump to the nth line by typing {n}G
* gotoLine is now 1-based, so to go to the first line you would use
pager.gotoLine(1)
* it is now allowed to return a function from a keybinding (which will be
subsequently executed as a regular keybinding)
|
|
|
|
|
| |
Just as in vi, 0 puts the cursor at the beginning of the current line,
and ^ puts the cursor at the position of the first non-blank character.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This makes it so that host = 'example\.org' mandates an exact match,
but host = '^example' matches example.org, example.com, etc.
(Previously, 'example\.org' would have matched exampleexample.org
as well, which was quite counter-intuitive.)
|
|
|
|
|
|
|
|
| |
* Use the output charset in lineedit (as w3m does)
* encoder: fix broken UTF-8 encoding, use openArray instead of var
seq for input queue
* Add RuneStream as an in-memory interface to EncoderStream
* Document display-charset config option
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
So that the default config actually works again. Also some doc updates.
|