| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Lets us skip a couple pointless multiplications/divisions during layout.
|
|
|
|
| |
Only glibc starts from the file's beginning with "a+".
|
| |
|
|
|
|
|
| |
The test case attached is undefined in CSS 2.1, but css-sizing-3
wants us to just ignore the width property (I think).
|
|
|
|
|
|
|
| |
this is necessary too, now that I think of it
(well, table caption sizing is still half-broken, but that's a problem
for another day...)
|
| |
|
| |
|
|
|
|
|
| |
judging from the symlink, I probably meant to do this but forgot to
finish it
|
|
|
|
|
| |
If the contents are larger than the specified cell height, then it is
simply ignored.
|
| |
|
|
|
|
| |
it should put it after the old items, not before them.
|
|
|
|
| |
Uses an additional lower-case map for O(1) case-insensitive comparisons.
|
|
|
|
| |
makes it easier to hide them
|
|
|
|
|
| |
now I sort of understand how it works. basically maxh and maxw represent
the inner area occupied by the widget at any time.
|
|
|
|
|
|
|
|
| |
* correct action on M-b
* add external.bookmark option
* move openFileExpand functionality into unquote
* add menu items
* update docs
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Finally it's done. It's basically w3mbookmark, but using Markdown
instead of HTML and in POSIX shell instead of C.
As a bonus, it can also (sort of) import w3mbookmark's output. Well,
at least it worked on my bookmark file, but there is a known issue with
bracket escaping... if it goes wrong, it's simple enough to edit it
manually :P
|
|
|
|
|
|
|
|
| |
Both are quite useful.
readFile and writeFile got a small makeover in error handling; in
particular, readFile now returns null instead of the empty string when
the file is missing and writeFile throws a TypeError on I/O errors.
|
|
|
|
|
|
|
|
|
|
|
| |
Implemented using proprietary selectors -cha-first-node and
-cha-last-node, modeled after -moz-first-node and -moz-last-node.
I think they are compatible.
That does mean this is more limited than w3m's trimming, e.g. it can't
really deal with nesting or empty tags. I think this is fine, as it's
mainly meant for unstyled documents in the first place (which are
unlikely to have e.g. MAIN tags).
|
| |
|
| |
|
|
|
|
| |
Since text is the fallback, just make it the default.
|
|
|
|
| |
file:/// is the standard serialization.
|
|
|
|
|
|
|
|
| |
Cookie jar separation is already enough to mitigate tracking issues
in this case. (Also, the fact that third-party-cookie controlled this
made things even more confusing.)
Also, add the previously missing host-only flag.
|
|
|
|
|
|
|
|
| |
Not quite sure why I had assumed that this is broken. At least on XTerm,
the previous behavior definitely was, e.g. with a white-ish background
and white foreground it would end up correcting the contrast to purple
even with black CSS color (thus breaking the "no fgcolor with bgcolor"
assumption anyway.)
|
| |
|
|
|
|
|
|
|
| |
Instead, just define the actual value over the getter function on the
first use.
Also, avoid accidentally creating the attributes NamedNodeMap on adopt.
|
|
|
|
|
|
| |
using div instead of / is sort of weird, but it makes it clearer if
we're dividing floats or layoutunits (and is already what the code
uses).
|
| |
|
|
|
|
| |
I no longer need it
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* fix broken newline skipping logic in consume
* remove reconsume char buffer (it's not needed with mmap)
* pass on backslash to unquote - this makes backslashes in
unquoteCommand work as expected (since it parses the command again)
* close ps on write failure
* add entries even before parse error - this drops a pointless copy of
mailcaps. (we could theoretically just use old behavior without the
copy, but this feels more intuitive anyway)
|
|
|
|
|
| |
"Computed" was redundant; other types of values don't have a common
type.
|
|
|
|
| |
we hadn't before, and it's annoying when using cha as a pager
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the past, Chawan would read global mailcap (/etc/mailcap, ...) too,
but every now and then that would run entries that I didn't even know
existed and definitely didn't intend to run. So I changed it to only
use ~/.mailcap, but this meant users now had to add mailcap entries for
every single mime type.
At some point I also changed application/octet-stream to always save to
disk, which is usually nice except when a text file is misrecognized as
binary. Often times I just want to decide myself what to do.
So now there are two layers. First, the global mailcap files (path as
per RFC) prompt before executing. Then there is ~/.chawan/auto.mailcap
(or ~/.config/chawan/auto.mailcap) which runs entries automatically.
If you press shift before selecting an option in the prompt, the
corresponding entry gets copied to auto.mailcap. It's also possible to
type a new entry on the fly. Overall I think it's quite convenient.
One unfortunate side effect is that existing users will have to migrate
their entries to auto.mailcap, or redefine external.auto-mailcap to e.g.
~/.mailcap, but this seems acceptable.
|
|
|
|
| |
POSIX does not guarantee that an error is negative.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
isearch feels quite janky in general, and I think there's still a race
lurking here... for now it's ok, but like buffer display, this really
belongs in a state machine (not promises)
|
| |
|
| |
|
|
|
|
| |
We can do this now that xminwidth is more accurate.
|
|
|
|
| |
better
|
|
|
|
| |
still not quite right, but it's slowly taking shape
|