| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | |
| |
| |
| |
| |
| |
| |
| | |
../../foot/config.c:154:50: error: format string is not a string literal (potentially insecure) [-Werror,-Wformat-security]
log_msg(log_class, LOG_MODULE, file, lineno, formatted_msg);
^~~~~~~~~~~~~
../../foot/config.c:154:50: note: treat the string as an argument to avoid this
log_msg(log_class, LOG_MODULE, file, lineno, formatted_msg)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Result is set through a pointer passed as an argument. Note that we
assume enums are 32-bit, and explicitly cast them to int*.
Static asserts have been added to ensure this invariant holds.
|
| | |
| |
| |
| | |
Add UNREACHABLE() at the bottom
|
| | | |
|
| | |
| |
| |
| |
| | |
This allows us to pass the final pointer directly to the conversion
functions, as well as allowing us to print outside-range errors.
|
| | |
| |
| |
| | |
Takes a pointer to a char*, free:s it, and strdups the current value.
|
| | |
| |
| |
| |
| | |
Write boolean value to a pointer passed as argument, return conversion
success/failure
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
These work like LOG_AND_NOTIFY_* but add contextual information: path
of the conf file, line number, section name, key/option name and the
value.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
* str_to_double() -> value_to_double()
* str_to_pt_or_px() -> value_to_pt_or_px()
|
| | |
| |
| |
| |
| |
| | |
* str_to_ulong() -> value_to_ulong()
* str_to_color() -> value_to_color()
* str_to_two_colors() -> value_to_two_colors()
|
| | | |
|
| | |
| |
| |
| | |
Change argument to a ‘struct context’ pointer
|
| |/ |
|
| |
|
|
|
|
|
|
|
| |
There's no need to call setlocale() twice, since the first call
returns the same value as the second.
We also handle a NULL return value explicitly and show a distinct
error message for that case, since it typically indicates a
misconfigured locale and not just a non-UTF8 locale.
|
| |
|
|
| |
Fixes compilation on systems with “too old” wayland-protocols
|
| |
|
|
|
| |
The bundled PKGBUILD has been pretty much identical to the one in the
AUR package “foot-git” for a long time now.
|
| | |
|
| |\
| |
| |
| | |
Closes #779
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
If there aren’t any seats available, input is not possible (neither
keyboard nor mouse input).
Note that this is not the same thing as e.g. no keyboard being plugged
in. In this case, there will be a seat, but without the keybaord
capability. Input may not be possible _right now_, but may be later,
if the user plugs in a keyboard.
Closes #779
|
| |\ |
|
| |/
|
|
|
|
|
|
|
|
|
| |
This is an application of the xdg activation protocol that will allow
compositors to associate new foot toplevels with the command that
launched them.
footclient receives an activation token from the launcher which the
compositor can use to track application startup. It passes the token
to the foot server, which then activates the new window with the token
to complete the startup sequence.
|
| |
|
|
| |
path:lineno: [section].key: value: message desribing what’s wrong with value
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
MSG_NOSIGNAL Requests not to send the SIGPIPE signal if an attempt
to send is made on a stream-oriented socket that is
no longer connected. The [EPIPE] error shall still be
returned.
|
| |/ |
|
| |\ |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we’re using CSDs, we’ve up until now rendered a 5px invisible
border. This border handles interactive resizing. I.e. hovering it
changes the mouse cursor, and mouse button events are used to start an
interactive resize.
This patch makes it possible to color part of (or the entire) border,
with a configurable color.
To facilitate this, two new options have been added:
* csd.border-width
* csd.border-color
border-width defaults to 0, resulting in the look we’re used to.
border-color defaults to the title bar color. If the title bar color
hasn’t been set, it defaults to the default foreground color (just
like the title bar color does).
This means that, setting border-width but not border-color, results in
a border that blends with the title bar.
|
| | |
|
| |\ |
|
| |/
|
|
|
|
|
|
|
|
| |
* Allow scrolling on the normal (non-alt) screen, when application is
grabbing the mouse (when user presses Shift).
* Use term_mouse_grabbed() instead of explicitly checking for
MOUSE_NONE tracking.
* Remove mouse tracking check from cmd_scrollback_{up,down}. Caller is
expected to have done the check.
* Don’t scroll down on mouse wheel tilt events.
|
| |\
| |
| |
| | |
Closes #765
|
| |/
|
|
|
|
|
| |
Key combinations assigned to this action will not be sent to the
application.
Closes #765
|
| |
|
|
|
| |
I presume "can be used here as well" was meant.
Spotted it while reading the docs.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Foot has been signaling window urgency through the (new) “XDG
activation” protocol for some time now. Update the documentation to
reflect this.
|
| | |
|
| | |
|
| |\
| |
| |
| | |
Closes #753
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The serial is used when copying/pasting data from the clipboard. Up
until now, we’ve used the serial from the keyboard/mouse enter
events.
This works in most cases, but breaks in the following example:
$ wl-copy WLCOPY
/* Ctrl+Shift+v works fine (pastes "WLCOPY") */
$ printf "\033]52;c;eHl6\a"
/* Ctrl+Shift+v pastes "WLCOPY" instead of "xyz" */
Shifting focus away and then back to the foot window, and re-executing
the printf works, suggesting the “enter” serial is no longer valid
after another process(?) has copied something to the clipboard.
Updating the serial on key press/release (and the corresponding mouse
serial on mouse button events) seems to fix this.
I’ve also tested that “normal” copy/paste operations, within the same
foot instance, and between foot and other applications, are still
working. In at least river (wlroots based), and GNOME/mutter.
Closes #753
|
| | | |
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| | |
The empty literals in the macro are to ensure the argument itself
is a string literal, so it can't be used on anything else.
|
| |\ \ |
|
| | | | |
|
| |\ \ \
| |/ /
|/| | |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| | |
This matches the documented (and observed) behavior in xterm:
> XTerm accepts either BEL or ST for terminating OSC sequences, and
> when returning information, uses the same terminator used in a query
-- https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-Operating-System-Commands
|
| |\ \
| |/
|/|
| | |
Closes #752
|
| |/
|
|
|
|
|
|
| |
This fixes an issue where pasting (using e.g. OSC-52) in client
applications that doesn’t do this conversion themselves, like tmux,
doesn’t work.
Closes #752
|
| |\ |
|
| |/ |
|
| |
|
|
|
|
|
|
|
| |
Grapheme shaping is now enabled by default in foot. However, when
generating the profiling data in PGO builds, this results in skewed
optimizations.
The end result is worse benchmark results regardless of whether
grapheme-shaping is enabled or not (when running the benchmarks).
|
| | |
|
| | |
|
| |
|
|
|
| |
* Tell people to search existing bugs first (open + closed)
* Re-order instructions: most important ones first
|
| |
|
|
|
| |
* Tell people to search existing bugs first (open + closed)
* Re-order instructions: most important ones first
|
| |\ |
|
| |/
|
|
|
|
|
|
| |
This changes the default value of tweak.grapheme-shaping to “yes”,
thus enabling grapheme shaping by default.
It also changes the default value of tweak.grapheme-width-method to
“wcswidth”, for maximum compatibility with terminal applications.
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Using underlining for parameters allows the angle brackets to be
removed while still keeping a visual separation between literals
and parameters. The removes any uncertainty about whether the
angle brackets are part of the sequence or not. It also mirrors
the formatting used further down in the document.
|
| |/
|
|
|
| |
The other tables that contain only params also use the heading
"Parameter" rather than "Sequence".
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Without pixman renderer override pgo builds in cage/sway require
access to actual render devices. In Gentoo's case the builds are run
as ordinary user and within a "sandbox" which prevents and logs access
outside of predefined places during build.
So let's default to pixman renderer for the PGO builds. Hopefully that
won't matter for the pgo optimizations to do the right thing within foot.
|
| | | |
|
| |/ |
|
| |\ |
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
foot doesn't show desktop notifications (via OSC777) if the current
terminal has keyboard focus.
This is probably a sane default, but there are use cases where showing
a notification regardless of the focus status may be desired. For
example, a completion notification of a long running task inside a
non-focused tmux window.
This PR adds the notify-focus-inhibit option which can be used to
disable inhibition of notifications when the window has focus.
The default value is `yes`, which retains the old behavior.
|
| |\ \ \
| |/ /
|/| |
| | | |
Closes #736
|
| |/ /
| |
| |
| | |
Closes #736
|
| |/ |
|
| |
|
|
|
|
|
| |
When reading XKB modifier state, use XKB_STATE_MODS_EFFECTIVE, not
XKB_STATE_MODS_DEPRESSED.
This fixes handling of ‘sticky’ modifier keys.
|
| | |
|