| Commit message (Collapse) | Author | Age | Lines |
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Having them as error messages was nice when we where still missing
lots of sequences.
Now we don't anymore, and these just spam stdout as well as syslog
when e.g. cat:ing binary data.
|
| |
|
|
|
|
| |
In most states, most 8-bit values are no-ops. This is already handled;
action() recognizes ACTION_NONE as a no-op. Thus, all we need to do is
remove the assertion.
|
| |
|
|
|
|
|
| |
We've just re-set the grid offsets, meaning rows 0..term->rows may not
all have been initialized.
Call grid_row_and_alloc() to ensure they are.
|
| |
|
|
|
| |
Mouse tracking always reports clicks, so using a cursor that suggests
you can click makes sense I think.
|
| |
|
|
|
|
|
|
|
|
| |
Show 'text' cursor when:
* we have no mouse tracking enabled
* forced selection has been enabled (shift being held down)
* We're *not* scrollback searching
In all other cases, show the 'left_ptr' cursor.
|
| |
|
|
| |
And update xcursor. This is currently not necessary, but doesn't hurt.
|
| | |
|
| |
|
|
|
|
| |
And update xcursor. This is necessary since we may still have mouse
focus. But without keyboard focus, we don't display the 'text'
xcursor.
|
| | |
|
| |
|
|
|
| |
This fixes an assertion when hovering over the input field for
scrollback searches.
|
| |
|
|
| |
This means we don't have to e.g. roundtrip when setting the cursor.
|
| | |
|
| | |
|
| |
|
|
|
| |
But if it isn't set, only estimate it if the font is a *scalable*
non-outline (bitmap) font.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Sway 1.2 has been seen to send pointer_button events without first
having sent pointer_enter.
|
| | |
|
| |
|
|
|
|
| |
When the user had configured the cursor color, we failed to
invert (reverse) the foreground and background color when the cursor
was on a cell with the 'reverse' attribute set.
|
| |
|
|
|
|
|
|
|
| |
When trying to write (to e.g. the slave, or to a clipboard receiver),
we first try to send the data synchronously, and only if that fails do
we switch to asynchronous mode.
However, the first synchronous may (in fact, is likely to) succeed
partially.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
But only do this when the font is scalable but not an outline. This is
only true for color bitmap fonts (emoji fonts), and not e.g. regular
bitmap fonts.
|
| |
|
|
| |
This is the fontconfig default as well
|
| | |
|
| |
|
|
| |
TODO: use actual output PPI. Question is *which* output...
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Since we're working with pixel sizes anyway...
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we receive a keyboard_key or pointer_motion event without first
having received a keyboard_enter or pointer_enter event (that being
the "sway bugs" part), we generally don't know _which_ terminal window
the event was intended for.
However, if we only have *one* window open (always the case for a
regular 'foot' process, or when there's a single footclient connected
to a foot server process), then obviously we can "guess" which window
the event was intended for... so do that.
Now, the only time the event is ignored is when we're a server process
with more than one window open (= more than one footclient connected).
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
I.e. what we're effectively doing is *not* repeating modifier
keys.
Besides being the "right" thing to do, this also works around another
Sway 1.2 bug, where being in a focused foot window and then switching
to a vt and back would cause us to be stuck in an endless key repeat
loop that would only stop when unfocusing, focusing back and then
unfocusing once again.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sway 1.2 has been seen sending keyboard_key() events without first
sending a keyboard_enter() event.
This can be triggered by:
1. start a foot terminal
2. unfocus it (move focus to another window)
3. switch to a vt
4. switch back to sway
5. focus the foot terminal
At this point, Sway will *not* send the keyboard_enter() event, but
instead send a keyboard_key() event.
(furthermore, if you now unfocus the window again, sway will send a
keyboard_leave() event, still without having sent a keyboard_enter()
event).
Sway has _also_ been seen crashing in wl_pointer_motion(). Though this
was in a build without proper debug information, everything points to
a similar issue - i.e. sway is sending a motion event without first
having sent an enter event.
Workaround this by detecting this and logging a warning the first time
it happens. The event is then ignored.
|
| | |
|
| |
|
|
|
| |
When there's no selection, exit early to avoid trying to get grid data
from row -1.
|
| | |
|
| |
|
|
|
|
|
| |
This fixes an assertion when holding in ctrl+shift+c (copy to
clipboard); subsequent "presses" would set the clipboard serial to 0,
which we would then assert on in the next iteration when we tried to
cancel the previous copy.
|
| |
|
|
|
|
|
|
|
|
| |
When we're shutting down a terminal, we destroy our Wayland window,
and assume that will unmap us.
There are cases when this isn't true (most likely when e.g. a screen
locker is active, and the unmap is being deferred).
Handle by explicitly setting focused to NULL.
|
| |
|
|
|
|
|
|
| |
This happens on Sway when exiting a screen locker. Or at least that's
when we see the problem; it's unclear if the event occurs when
starting the screen locker, or when exiting it. Or maybe its both.
Anyway, don't try to unfocus a NULL-terminal.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Since fonts are destroyed and removed from the font cache when the
last instance is destroyed, closing the "last" terminal window in
server mode would destroy the fonts, and their glyph caches.
By instantiating the set in main, we ensure the fonts, and the glyph
caches, remain. This makes launching new terminals (much) faster.
Note that in "normal" (non-server) mode, this isn't really necessary,
but also doesn't have any penalty.
|
| | |
|
| |
|
|
|
|
|
|
| |
This reverts commit 7c2dd936905de7aa21a483646b3765cd8d59eb4e.
Or repeated pkgbuilds will fail since the first meson call
doesn't *re*configure an already configured build tree, causing us to
build with pgo=use when we should be using pgo=generate.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 739c5cf7f026bd7792f94276e8d6b2587a6ff597.
The original commit stated:
Not sure why these were added here; they don't appear to be
needed (we're writing to the client - it's up to the client to echo
stuff, in which case we redraw as usual).
But, client output doesn't cause a scrollback/view reset.
|
| | |
|
| |
|
|
| |
Otherwise the build fails in the pgo=use phase.
|
| |
|
|
| |
This avoids a meson re-configure right off the bat.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
'p' means 'primary', while 's' means 'selection'. Thus, a client can
now request 'selection' clipboard data and will receive it from the
primary selection.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
footclient (`client.c`, to be precise) includes `version.h`, which is
a generated file.
|
| | |
|
| |
|
|
|
| |
hts - Horizontal Tab Set (?)
tbc - Tab Clear
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Report us as being VT220, as VT420 causes vttest to send a
DECRQSS. This is a DCS request that we don't implement (there's no DCS
handling *at all* - all DCS strings are ignored).
Should be ok as no one appears to care about this one. Other terminals
report a much lower level (urxvt for example, replies with vt100. We
used to reply with vt102, which also was fine).
|
| |
|
|
|
|
|
| |
Pretend we're a VT420, with a couple of supported features
indicated. Note that I haven't verified we support *everything* that
each features entails - or even what exactly a feature *is* (locator
port?)
|
| | |
|
| |
|
|
| |
By replying with "Device OK"
|
| |
|
|
|
|
| |
In the legacy mouse reporting mode, line and column numbers are
limited to 223 (255-32). In case the current coordinate falls outside
this, simply ignore it (don't report it).
|
| | |
|
| |
|
|
|
| |
This mouse mode is never enabled. I.e. we don't support it. Add
asserts to catch usage of it, should we ever decide to implement it.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
When support was added for DECOM (absolute/relative row addressing), a
small but noticeable (~3.5%) performance regression was introduced.
Try to improve the situation by simplifying the relative-to-absolute
conversion; only the row needs to be transformed.
|
| |
|
|
| |
This reverts commit 686405b7031736445eeb35206e4a797a8dd78d91.
|
| |
|
|
| |
This reverts commit fd8a3992745b9ec51b6e6c1dfc39faf01369b680.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Adds a linebreak (+ scroll if necessary) if we're in a deferred wrap
and auto-margins are enabled.
Return true when we wrapped, false otherwise.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
* It takes a parameter, that indicates the number of tab stops to move
through
* Use the tab stops defined in the tab stops list, not hard coded mod
8 columns.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
There were actually two bugs here:
* When checking for a tab stop, make sure the new tab stop is at a
different column. Otherwise you can't tab away from a tab stop.
* When there aren't any tab stops configured, or when we're already
beyond the last tab stop, then tab to the last column (at least I
think that's what we're supposed to do).
|
| | |
|
| | |
|
| | |
|