| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
| |
This is very much a work in progress, though functional.
Qt Widgets are basically non-working on Android,
though Qt Quick requires a radically different approach.
|
| |
|
|
|
|
|
| |
It is fairly mediocre all around, but also generally usable,
natively covering mobile platforms.
|
| |
|
| |
|
|
|
|
|
| |
Some work remains to be done to get it to be even as good
as the Win32 frontend, but it's generally usable.
|
|
|
|
|
|
|
| |
This has been more of an exercise. The performance of Msftedit.dll
is rather abysmal, and its interface isn't the most accomodating.
That said, the frontend is quite usable, at least on Windows 10+.
|
| |
|
| |
|
|
|
|
| |
Just like xS. 2.0.0 is the ideal time for such a breaking change.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
It's been five years since the previous xC screenshot was made.
|
|
|
|
|
|
|
|
|
| |
There seem to be only a few things it could bring to the table,
compared to xP, making it barely worth the effort:
- saner keyboard controls,
- GVIM integration,
- slightly improved resource usage.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
And translate them for frontends.
This is very long overdue, and a rather significant cleanup.
Bump liberty.
|
|
|
|
| |
And more or less finalize out the protocol for this use case.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For this, we needed a wire protocol. After surveying available options,
it was decided to implement an XDR-like protocol code generator
in portable AWK. It now has two backends, per each of:
- xF, the X11 frontend, is in C, and is meant to be the primary
user interface in the future.
- xP, the web frontend, relies on a protocol proxy written in Go,
and is meant for use on-the-go (no pun intended).
They are very much work-in-progress proofs of concept right now,
and the relay protocol is certain to change.
|
|
|
|
| |
Stop pretending that xD has a future.
|
| |
|
|
|
|
| |
Now it's a realistically useful frontend.
|
|
|
|
|
|
|
|
|
|
|
| |
This commit constitutes a breaking change to old configurations.
All behaviour.* options have now become general.*, with the following
few renames as exceptions:
- editor_command -> editor
- backlog_helper -> pager
- backlog_helper_strip_formatting -> pager_strip_formatting
|
| |
|
| |
|
|
|
|
| |
It is about to see some extensions, obsoleting the number three.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
I'm not entirely sure, but it looks like some people might not like
jokes about the Holocaust.
On a more serious note, the project has become more serious over
the 7 or so years of its existence.
|
|
|
|
|
|
|
| |
So far it's only been mentioned in the NEWS file,
which is definitely not sufficient.
It would be good to move this kind of stuff out from README.adoc.
|
|
|
|
|
|
|
|
| |
When fancy-prompt.lua is enabled, tho prompt is two-lined
and a simple PageUp would skip one line of content.
It works slightly better than it should: when there's under
a page of content to scroll, there is no shift at all.
|
| |
|
|
|
|
|
|
| |
There's nothing experimental about this project anymore. It's stable.
Maybe we should add a photo of Hitler or something.
|
|
|
|
| |
To some extent they duplicate the README but from a different angle.
|
| |
|
|
|
|
| |
There is still one outstanding issue with the backlog helper, though...
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
I've come to the conclusion that copyright mostly just stands in the way
of software development. In my jurisdiction I cannot give up my own
copyright and 0BSD seems to be the closest thing to public domain.
The updated mail address, also used in my author/committer lines,
is shorter and looks nicer. People rarely interact anyway.
|
|
|
|
| |
"Edgy" is actually a fitting word. And we've lost OBS!
|
| |
|
|
|
|
| |
So be it, SJWHub, at least I have a reason to move.
|