<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git/config.h, branch 1.6.2</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=1.6.2</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=1.6.2'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2020-12-17T11:05:22Z</updated>
<entry>
<title>fonts: size fonts using the scaling factor when output scaling is enabled</title>
<updated>2020-12-17T11:05:22Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-17T11:05:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=0a821f2ed44f46086650a20a39c28f077d954aa2'/>
<id>urn:sha1:0a821f2ed44f46086650a20a39c28f077d954aa2</id>
<content type='text'>
This extends the new ‘dpi-aware’ option with a new default value,
‘auto’.

When set to ‘auto’, fonts are sized using monitors’ DPI when output
scaling is disabled. When output scaling is enabled, fonts are instead
sized using the scaling factor.

The reasoning here is that a user that has enabled output scaling is
obviously *not* relying on DPI scaling.

Output scaling can also be a way to compensate for different viewing
distances, in which case we do *not* want to break that by using DPI
scaling.

Users can still force DPI-only font sizing by setting ‘dpi-aware=yes’,
or disable it completely by setting ‘dpi-aware=no’.
</content>
</entry>
<entry>
<title>config_font_parse(): return fail/success</title>
<updated>2020-12-15T17:55:27Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-15T17:55:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=0d6b5f522ed755aca8a85c005962fb03232b4c96'/>
<id>urn:sha1:0d6b5f522ed755aca8a85c005962fb03232b4c96</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config: add ‘notify’ to possible values for ‘bell’ in foot.ini</title>
<updated>2020-12-10T17:22:48Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-10T17:22:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=15d20af2a24664b09604f1ec5f121c38f1500c32'/>
<id>urn:sha1:15d20af2a24664b09604f1ec5f121c38f1500c32</id>
<content type='text'>
When `bell=notify`, foot will trigger a desktop notification when it
receives a BEL in an unfocused window.
</content>
</entry>
<entry>
<title>osc: implement urxvt’s “OSC 777;notify”</title>
<updated>2020-12-09T19:54:51Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-08T18:19:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=21cc68d49e94f3a385afc2bf59c5f7d88f9ad802'/>
<id>urn:sha1:21cc68d49e94f3a385afc2bf59c5f7d88f9ad802</id>
<content type='text'>
OSC 777 is URxvt’s generic escape to send commands to its perl
extensions. The first parameter is the name of the extension, followed
by its arguments.

OSC 777;notify is a, if not well established, at least a fairly well
known escape sequence to request a (desktop) notification. The syntax
is:

  \e]777;notify;&lt;title&gt;;&lt;body&gt;\e\\

Neither title nor body is escaped in any way, meaning they should not
contain a ‘;’.

Foot will split title from body at the *first* ‘;’. Any remaining ‘;’
characters are treated as part of ‘body’.

Instead of adding built-in support for the freedesktop notification
specification (which would require us to link against at least dbus),
add a new config option to foot.ini: ‘notify’.

This option specifies the command to execute when a notification is
received. ‘${title}’ and ‘${body}’ can be used anywhere, in any
combination, and as many times as you want, in any of the command
arguments.

The default value is ‘notify-send -a foot -i foot ${title} ${body}’
</content>
</entry>
<entry>
<title>config: replace union in config struct with simple width/height members</title>
<updated>2020-11-30T02:24:38Z</updated>
<author>
<name>Craig Barnes</name>
<email>craigbarnes@protonmail.com</email>
</author>
<published>2020-11-30T02:24:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=adde947fc5ffc3d143040a984d0907262ac279bc'/>
<id>urn:sha1:adde947fc5ffc3d143040a984d0907262ac279bc</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config: add ‘dpi-aware’ option, defaulting to enabled</title>
<updated>2020-11-19T18:25:48Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-11-17T16:59:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=8e7658a135ae05c790094f2b1b681c7f64f05cf0'/>
<id>urn:sha1:8e7658a135ae05c790094f2b1b681c7f64f05cf0</id>
<content type='text'>
When disabled, foot no longers uses outputs’ DPI to scale the
font. Instead, it uses the outputs’ scaling factor.

That is, instead of appending “:dpi=123” to the fontconfig string,
modify the “:pixelsize” or “:size” attribute.

Closes #206
</content>
</entry>
<entry>
<title>config: add default.bold-text-in-bright option</title>
<updated>2020-11-14T10:22:19Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-11-14T10:21:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=34abf665e266a3285caf2a5c9b65bc93d88b3af7'/>
<id>urn:sha1:34abf665e266a3285caf2a5c9b65bc93d88b3af7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config: add support for pipe-* actions in mouse bindings</title>
<updated>2020-11-06T18:30:05Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-11-06T18:29:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=9ce79e2ef0b0b19b06990302807d6c3b3a755e1e'/>
<id>urn:sha1:9ce79e2ef0b0b19b06990302807d6c3b3a755e1e</id>
<content type='text'>
Closes #183
</content>
</entry>
<entry>
<title>config: add font-bold, font-italic and font-bold-italic options</title>
<updated>2020-10-20T19:04:47Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-10-20T19:04:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=2c101a21ee6df096dadd60a77b4cb190f8503490'/>
<id>urn:sha1:2c101a21ee6df096dadd60a77b4cb190f8503490</id>
<content type='text'>
These options lets the user configure custom fonts and styles, to use
with the bold and italic cell attributes.

By default, they are unset, meaning we use the bold/italic variants of
the regular font.

Closes #169.
</content>
</entry>
<entry>
<title>csi: implement ‘CSI ? 1042 h/l’ - enable/disable bell-is-urgent</title>
<updated>2020-10-11T15:44:29Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-10-11T15:44:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=17761dce63100d287b62dda5bf2c49d5db5f2576'/>
<id>urn:sha1:17761dce63100d287b62dda5bf2c49d5db5f2576</id>
<content type='text'>
</content>
</entry>
<entry>
<title>conf: csd.preferred can now be set to ‘none’</title>
<updated>2020-10-10T11:07:29Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-10-10T09:04:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=6ff97128fc55573274fb21b6e56821db02cf162b'/>
<id>urn:sha1:6ff97128fc55573274fb21b6e56821db02cf162b</id>
<content type='text'>
When csd.preferred == none, we will request CSDs from the compositor,
but internally render as if we are using SSDs. That is, we don’t
render any window decorations at all.

Note that some compositors may ignore our request to use CSDs, and
still render SSDs for us.

Closes #163
</content>
</entry>
<entry>
<title>config: add ‘[default].word-delimiters’</title>
<updated>2020-10-09T17:44:23Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-10-09T17:44:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=49f4b3da64d45cee04295ce005ff0399fcfeebe2'/>
<id>urn:sha1:49f4b3da64d45cee04295ce005ff0399fcfeebe2</id>
<content type='text'>
This option lets the user configure which characters act as word
delimiters when selecting text.

This affects both “double clicking”, and ‘ctrl-w’ in scrollback search
mode.

Closes #156
</content>
</entry>
<entry>
<title>bell: optionally render margins in red when receiving BEL</title>
<updated>2020-10-08T17:55:32Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-10-08T17:55:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=7c6686221f328e9399eb679c246662c801b2356b'/>
<id>urn:sha1:7c6686221f328e9399eb679c246662c801b2356b</id>
<content type='text'>
Add anew config option, ‘bell=none|set-urgency’. When set to
‘set-urgency’, the margins will be painted in red (if the window did
not have keyboard focus).

This is intended as a cheap replacement for the ‘urgency’ hint, that
doesn’t (yet) exist on Wayland.

Closes #157
</content>
</entry>
<entry>
<title>config: add mouse.alternate-scroll-mode option</title>
<updated>2020-09-15T17:12:29Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-09-15T17:09:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=f2497320c68978fb4c25226966c11f115cb88e10'/>
<id>urn:sha1:f2497320c68978fb4c25226966c11f115cb88e10</id>
<content type='text'>
This option controls the initial state of the Alternate Scroll Mode,
and defaults to ‘enabled’.
</content>
</entry>
<entry>
<title>config: add tweak.scaling-filter</title>
<updated>2020-09-13T15:59:56Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-09-13T15:59:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=51a7e44fa295b95404cb9b9373fb9b9a44664fda'/>
<id>urn:sha1:51a7e44fa295b95404cb9b9373fb9b9a44664fda</id>
<content type='text'>
Use the new fcft_set_scaling_filter() API to use a non-default scaling
filter.

By default, we use lanczo3, the ‘best’ filter. This overrides the
default in fcft, which is ‘cubic’ filtering.
</content>
</entry>
<entry>
<title>Add -W,--window-size-chars, and foot.ini:initial-window-size-chars</title>
<updated>2020-09-08T17:41:00Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-09-08T17:17:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=eb6737ca2593f457368ae16e920911cdd70a2e33'/>
<id>urn:sha1:eb6737ca2593f457368ae16e920911cdd70a2e33</id>
<content type='text'>
* Add -W,--window-size-chars command line option
* Add initial-window-size-chars foot.ini option
* Add -w,--window-size-pixels command line option
* Add initial-window-size-pixels foot.ini option
* Deprecate -g,--geometry command line option in favor of
  -w,--window-size-pixels
* Deprecate geometry option in foot.ini in favor of
  initial-window-size-pixels
</content>
</entry>
<entry>
<title>config: add tweak.damage-whole-window</title>
<updated>2020-09-06T15:52:07Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-09-06T15:52:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=d040284cc78e753a0c44c35d8446622d453d4674'/>
<id>urn:sha1:d040284cc78e753a0c44c35d8446622d453d4674</id>
<content type='text'>
When enabled, foot will ‘damage’ the entire window, instead of just
the modified/updated rows.

This will force the compositor to redraw/blend the whole window.

This can be used to workaround an issue with fractional scaling in
Gnome, where random thin lines may appear.
</content>
</entry>
<entry>
<title>render: optionally enable heuristics that deal with private usage area chars</title>
<updated>2020-09-03T15:37:44Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-09-03T15:37:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b71016c25dc18a2c098a87439046873c6c9ddb30'/>
<id>urn:sha1:b71016c25dc18a2c098a87439046873c6c9ddb30</id>
<content type='text'>
Try to detect double-width *glyphs* for single-width *characters*, and
allow them to overflow into the next cell.

This is only done for single-width chars with a glyph width that is at
least 1.5 cells wide, but at most 3 cells.

The feature is gated by the new
‘tweak.allow-overflowing-double-width-glyphs’, and is disabled by
default.

Closes #116
</content>
</entry>
<entry>
<title>config: key/mouse bindings: refactor: less parsing in keyboard_enter()</title>
<updated>2020-08-13T16:47:19Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-08-10T17:00:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b97ef5819f806fe401a4b655bd06479a0394ea9d'/>
<id>urn:sha1:b97ef5819f806fe401a4b655bd06479a0394ea9d</id>
<content type='text'>
This simplifies the handling of mouse and keyboard bindings.

Before, the bindings where parsed *both* when loading the
configuration, and then on every keyboard enter event. This was done
since keys require a keymap to be decoded. Something we don't have at
configuration time. The idea was that at config time, we used a
default keymap just to verify the key combo strings were valid.

The following has changed:

* The bindings in the config struct is now *one* key combo per
  entry. Previously, it was one *action* per entry, and each entry
  had one or more key combos.

  Doing it this way makes it easier when converting the binding in the
  keyboard enter event (which previously had to expand the combos
  anyway).

* The bindings in the config struct no longer contains any unparsed
  strings.

  A key binding contains a decoded 'modifier' struct (which specifies
  whether e.g. ctrl, or shift, or ctrl+shift must be pressed for the
  binding to be used).

  It also contains a decoded XKB keysym.

* A mouse binding in the config struct is similar to a key binding,
  except it contains the button, and click count instead of the XKB
  key sym.

* The modifiers in the user-specified key combo is decoded at config
  time, by using the pre-defined XKB constants
  XKB_MOD_NAME_&lt;modifier&gt;.

  The result is stored in a 'modifiers' struct, which is just a
  collection of booleans; one for each supported modifier.

  The supported modifiers are: shift, ctrl, alt and meta/super.

* The key sym is decoded at config time using
  xkb_keysym_from_name(). This call does *not* depend on a keymap.

* The mouse button is decoded at config time using a hardcoded mapping
  table (just like before).

* The click count is currently hard-coded to 1.

* In the keyboard enter event, all we need to do is pre-compute the
  xkb_mod_mask_t variable for each key/mouse binding, and find all the
  *key codes* that map to the (already decoded) symbol.

  For mouse bindings, the modifiers are the *only* reason we convert
  the mouse bindings at all.

  In fact, on button events, we check if the seat has a keyboard. If
  not, we use the mouse bindings from the configuration directly, and
  simply filter out those with a non-empty set of modifiers.
</content>
</entry>
<entry>
<title>config: wip: add support for modifiers in mouse bindings</title>
<updated>2020-08-13T16:47:19Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-08-09T20:40:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=544c1b1976544085a2f27497c5c516bf1d9edfa3'/>
<id>urn:sha1:544c1b1976544085a2f27497c5c516bf1d9edfa3</id>
<content type='text'>
Mouse bindings can now include modifiers. They are specified in pretty
much the same way as in keyboard bindings:

  Control+BTN_LEFT
</content>
</entry>
</feed>
