aboutsummaryrefslogtreecommitdiff
path: root/CHANGELOG.md (follow)
Commit message (Collapse)AuthorAgeLines
...
* term: check visual-focus, not kbd-focus when enabling/disabling cursor blinkDaniel Eklöf2021-08-17-0/+3
| | | | | | | | | | | | term_cursor_blink_update() is called when the visual focus changes state (i.e. when our top-level surface is activated de-activated). Checking keyboard focus worked on Sway, but on e.g. GNOME, the order in which keyboard focus and visual focus are updated is different, and we ended up either making the cursor invisible, or visible, but not blinking, when changing focus back to the window. Closes #686
* changelog: mention keypad application mode keys being removedDaniel Eklöf2021-08-14-0/+4
|
* changelog: mention km/smm/rmm being removedDaniel Eklöf2021-08-14-0/+8
|
* pt-or-px: heed the dpi-aware settingDaniel Eklöf2021-08-13-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | Before this patch, pt-or-px values, like letter-spacing, were *always* scaled using the current DPI value. This is wrong; if the fonts are scaled using the output’s scaling factor, then so should all other point values. This also fixes an issue where e.g. letter-spacing would use one DPI value at startup, but then when increasing/decreasing or resetting the font size, would be re-calculated using a different DPI value, leading to completely different spacing. This happened when there were multiple monitors, with different DPI values, and foot guessed the initial DPI value wrong. Normally, foot would correct itself as soon as the window was mapped, and the “correct” DPI value known. But if the fonts were scaled using the scaling factor, it was possible that the font reload never happened. This patch also updates the thickness calculation (for LIGHT and HEAVY box drawing characters) to use the scaling factor when appropriate. Closes #680
* render: run the “overflowing glyphs” prepass *before* rendering sixelsDaniel Eklöf2021-08-11-0/+2
| | | | | | | | | | | | | | | | | | | | | | | This fixes an issue where the left-most column of a sixel was “overwritten” by the cell content. This patch also rewrites the prepass logic, to try to reduce the number of loads performed. The new logic loops each row from left to right, looking for dirty cells. When a dirty cell is found, we first scan backwards, until we find a non-overflowing cell. That cell is unaffected by the overflowing cell we’re currently dealing with. We can also stop as soon as we see a dirty cell, since that cell will already have been dealt with. Then, we scan forward, dirtying cells until we see a non-overflowing cell. That first non-overflowing cell is also dirtied, but after that we break. The last loop, that scans forward, advances the same cell pointer used in the outer loop.
* changelog: url.uri-charactersDaniel Eklöf2021-08-09-0/+2
|
* input: implement support for mouse wheel left/rightDaniel Eklöf2021-08-07-0/+1
| | | | | | | | | | | | | We now emit button 6/7 events (when the client application grabs the mouse). This buttons map to mouse wheel horizontal scroll events. Or, left/right tilting, if you like. Wayland report these as ‘axis’ events (just like regular scroll wheel events), and thus we need to translate those scroll events to button events. libinput does not define any mouse buttons for wheel tilts, so we add our own defitions. These are added last in the BTN_* range, just before the BTN_JOYSTICK events.
* Revert "terminfo: add ich1=\E[@"Daniel Eklöf2021-08-07-1/+0
| | | | | | This reverts commit 76fab8cf695b8e18e9f07d383189a34ca129e3ac. See https://codeberg.org/dnkl/foot/issues/668#issuecomment-246149
* terminfo: change kmous to \E[<, add XM+xm capabilitiesDaniel Eklöf2021-08-06-0/+2
| | | | | | | | | | | ncurses has had a bug where mouse support is completely disabled if the terminfo didn’t have kmous=\E[M, *or*, the terminfo *name* contained ‘xterm’. This appears to have been fixed. Thus, change kmous to \E[<, and set xm/XM accordingly. With this, ncurses application will use the SGR mouse reporting mode, instead of the legacy reporting mode.
* terminfo: add ich1=\E[@Daniel Eklöf2021-08-06-0/+1
|
* box-drawing: add U+1FB3C-U+1FB6F, U+1FB9A and U+1FB9BDaniel Eklöf2021-08-05-0/+3
| | | | | | These are the “wedges” from the Unicode 13 “Legacy Computing” symbols. Closes #474
* term: send SIGTERM/SIGKILL to the entire process groupDaniel Eklöf2021-07-31-0/+2
|
* changelog: asynchronous client application terminationDaniel Eklöf2021-07-31-0/+6
|
* config: include: add support for ~-expansionDaniel Eklöf2021-07-30-0/+2
| | | | Closes #659
* Only brighten palette colors with bold-text-in-bright=palette-basedDavid Rosca2021-07-26-0/+5
|
* changelog: initialize output scaling factor to 1Daniel Eklöf2021-07-26-0/+5
|
* wayland: prevent hang when terminating due to broken Wayland connectionDaniel Eklöf2021-07-24-0/+2
| | | | | | | | | | | | | | | | | | | | | If the call to fdm_wayl() with EPOLLHUP was followed by calls to wayl_roundtrip(), foot would hang. The reason for this is that the EPOLLHUP handler in fdm_wayl() would call wl_display_cancel_read(). wayl_roundtrip() also calls wl_display_cancel_read() (since we normally have called wl_display_prepare_read()), before calling wl_display_roundtrip(). When calling wl_display_cancel_read() two times in a row, without a wl_display_prepare_read() in between, wl_display_roundtrip() hangs. Fix by not calling wl_display_cancel_read() in fdm_wayl(). This ensures our invariant holds: wl_display_prepare_read() is *always* in effect outside of fdm_wayl(). Closes #651
* meson: add -Ddocs=disabled|enabled|auto command line optionDaniel Eklöf2021-07-24-0/+1
| | | | | When enabled (the default, if scdoc is found), we build and install the man pages, example foot.ini, readme, changelog and license files.
* changelog: window title in CSDsDaniel Eklöf2021-07-24-0/+5
|
* search: reset match state when selection is cancelledDaniel Eklöf2021-07-22-0/+3
| | | | | | | | | | | | While we’re in scrollback search mode, the selection may be cancelled (for example, if the application is scrolling out the selected text). Trying to e.g. extend the search selection after this has happened triggered a crash. This fixes it by simply resetting the search match state when the selection is cancelled. Closes #644
* pgo: fix PGO builds with clangDaniel Eklöf2021-07-22-0/+1
| | | | | | | | Add stubs for shm_chain_new(), shm_chain_free() and shm_unref(). This fixes ‘pgo’ linking failures in the ‘generate’ phase when doing a PGO build with clang. Closes #642
* render: prevent cells from overflowing into marginTimur Celik2021-07-20-0/+5
|
* changelog: add new ‘unreleased’ sectionDaniel Eklöf2021-07-18-0/+11
|
* changelog: prepare for 1.8.2Daniel Eklöf2021-07-18-4/+3
|
* changelog: remove entries that are no longer relevantDaniel Eklöf2021-07-18-4/+0
| | | | | The tweak.allow-overflowing-double-width-glyphs option have been superseded by tweak.overflowing-glyphs.
* term: erase_scrollback(): destroy sixels that touch the scrollbackDaniel Eklöf2021-07-18-1/+1
|
* changelog: crash when \E[3J was executed with a selection in the scrollbackDaniel Eklöf2021-07-18-0/+3
|
* render: Allow cells to bleed into their neighborTimur Celik2021-07-17-0/+11
| | | | | | | | | | | | | | | | This patch adds a `confined` flag to each cell to track if the last rendered glyph bled into it's right neighbor. To keep things simple, bleeding into any other neighbor cell than the immediate right one is not allowed. This should cover most use cases. Before rendering a row we now do a prepass and mark all cells unclean that are affected by a bleeding neighbor. If there are consecutive bleeding cells, the whole group must be re-rendered even if only a single cell has changed. The patch also deprecates both old overflowing glyph options *allow-overflowing-double-width-glyphs* and *pua-double-width* in favor of a single new one named *overflowing-glyphs*.
* Merge branch 'decsdm'Daniel Eklöf2021-07-16-0/+2
|\ | | | | | | Closes #631
| * csi: invert the meaning of DECSDMDaniel Eklöf2021-07-14-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There has been some confusion whether enabling DECSDM (private mode 80) enables or disables sixel scrolling. Foot currently enables scrolling when DECSDM is set, and this patch changes this, such that setting DECSDM now *disables* scrolling. The confusion is apparently due to a documentation error in the VT340 manual, as described in https://github.com/dankamongmen/notcurses/issues/1782#issuecomment-863603641. And that makes sense, in a way: the SDM in DECSDM stands for Sixel Display Mode. I.e. it stands to reason that enabling that disables scrolling. Anyway, this lead to https://github.com/hackerb9/lsix/issues/41, where it was eventually proven (by testing on a real VT340), that foot, and a large number of other terminals (including XTerm) has it wrong: https://github.com/hackerb9/lsix/issues/41#issuecomment-873269599.
* | url-mode: use shm_get_many()Daniel Eklöf2021-07-15-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If we have lots of URLs, we use up a *lot* of SHM buffers (and thus pools). Each and every one is a single mmap(), of at least 4K. Since all URL labels are created and destroyed at the same time, it makes sense to use a single pool for all buffers. To do this, we must now do two passes; first one to generate the actual string (label content), and to calculate the label sizes. Then we use this information to allocate all SHM buffers at once, from the same pool. Finally, we iterate the URLs again, this time to actually render them.
* | render: search: set clip regionDaniel Eklöf2021-07-15-0/+2
| | | | | | | | | | Fixes crash when the search box has been reduced in height, due to limited window space.
* | render: scrollback indicator: improve handling of very small window sizesDaniel Eklöf2021-07-15-0/+2
| |
* | changelog: box-drawing fixes on big-endianDaniel Eklöf2021-07-14-0/+2
|/
* url-mode: abort when running into un-allocated scrollback memoryDaniel Eklöf2021-07-11-0/+2
| | | | | | | | | | | | | | | | | | | | When tagging URL cells (in preparation for rendering URL mode), we loop the URL’s entire range, setting the `url` attribute of all cells, and dirtying the rows. It is possible to create URLs that are invalid, and wrap around the scrollback, even though the scrollback hasn’t yet been filled. For example, by starting an OSC-8 URL, moving the cursor, and then closing the OSC-8 URL. These URLs are invalid, but are still rendered just fine. “Fine” being relative - they will typically fill the entire screen. But at least that’s a very clear indication for the user that’s something is wrong. The problem is when we hit un-allocated scrollback rows. We didn’t check for NULL rows, and crashed. This has now been fixed.
* url-mode: fix crash when removing duplicate and/or overlapping URLsDaniel Eklöf2021-07-11-0/+2
| | | | | | | | | | | | | | | | Removing overlaping and duplicated URLs is done by running two nested loops, that both iterate the same URL list. When a duplicate is found, one of the URLs is destroyed and removed from the list. Deleting and removing an item *is* safe, but only as long as _no other_ iterator has references to it. In this case, if we remove an item from e.g. the inner iterator, we’ll crash if the outer iterator’s *next* item is the item being removed. Closes #627
* url-mode: purge SHM pixmaps when destroying URLsDaniel Eklöf2021-07-11-0/+2
| | | | | | | | | | Unlike other surface types, the SHM cookie depends on the address of each URL instance. This means if we enable, disable, and then enable URL mode again (thus showing exactly the same URLs as the first time), the URLs will have new addresses, and thus the old SHM pixmaps will not get purged automatically. So, manually purge them when destroying the URLs.
* config: add locked-title=no|yesDaniel Eklöf2021-07-04-0/+5
| | | | Closes #386
* term: rows printed to now defaults to having a hard linebreakDaniel Eklöf2021-07-03-0/+5
| | | | | | | That is, instead of requiring a ‘\n’ to be printed, non-empty lines are now treated as having a hard linebreak by default. The linebreak is cleared on an explicit wrap.
* allow-overflowing-double-width-glyphs: take glyph offset into accountDaniel Eklöf2021-07-02-0/+7
| | | | | | | | A narrow, but offset:ed glyph should still be considered double width. This patch also fixes a crash, when the maybe-double width glyph is in the last column. This is a regression.
* changelog: s/from/inDaniel Eklöf2021-07-01-1/+1
|
* changelog: add new ‘unreleased’ sectionDaniel Eklöf2021-07-01-0/+11
|
* changelog: prepare for 1.8.1Daniel Eklöf2021-07-01-5/+2
|
* changelog: move grapheme cluster width entry to ‘changed’, and rewrite itDaniel Eklöf2021-07-01-2/+7
|
* config: rename at-most-2 (value for grapheme-width-method) to double-widthDaniel Eklöf2021-07-01-1/+1
|
* config: add tweak.grapheme-width-method=wcswidth|at-most-2Daniel Eklöf2021-07-01-0/+3
|
* config: remove replaced/removed key bindings, instead of marking as ‘unused’Daniel Eklöf2021-06-30-0/+2
| | | | | | | | | | | | Instead of keeping removed/replaced key bindings in the key binding array (marked as ‘unused’), remove them, by compacting the array. The invariant is thus that there should be *no* entries in the key binding list with the `BIND_ACTION_NONE` for action. Add code to debug builds that verifies this, plus a unit test. Closes #614
* terminfo: add Tc, setrgbf and setrgbb capabilitiesCraig Barnes2021-06-29-0/+4
| | | | | | | | | | | | | | | | | | | | | These extensions are used by tmux and neovim, in order to make use of 24-bit colors without facing the problems that plague the `RGB` capability. This should allow 24-bit colors to work "out of the box" in tmux, without the usual workaround of adding: set-option -ga terminal-overrides ",foot*:Tc" ...to ~/.tmux.conf. See also: * https://github.com/kovidgoyal/kitty/commit/18fe2e8dfa34038aabd5c3a2fdb3624e2b27932a#commitcomment-31373962 * https://github.com/neovim/neovim/blob/f83c25942dd8b94ad5218ce78b9e6fb86d2f0358/runtime/doc/term.txt#L123-L139 * https://github.com/tmux/tmux/blob/b1a8c0fe022e99cffb0fb4f321740464f35bc6b9/CHANGES#L988-L989 Closes #615
* log: add LOG_CLASS_NONE and use as initializer for log_levelCraig Barnes2021-06-26-0/+6
| | | | | | | | | | | | This means that logging will be completely disabled until log_init() has been called, which is useful to prevent log spam when running UNITTEST{} blocks in debug builds. Note that this doesn't change the default log level at runtime, which was already being set to LOG_CLASS_INFO in main.c and client.c. The new log level is also exposed to the command-line interface as `--log-level=none`, which allows disabling logging entirely.
* vt: don’t reset utf8proc grapheme state when we’re not at a grapheme breakDaniel Eklöf2021-06-25-0/+4
|
* changelog: add new ‘unreleased’ sectionDaniel Eklöf2021-06-25-0/+11
|
* changelog: prepare for 1.8.0Daniel Eklöf2021-06-25-3/+2
|
* changelog: spelling; add missing ‘l’ in ‘experimental’Daniel Eklöf2021-06-24-1/+1
|
* changelog: describe what (does not) happens when grapheme-shaping=noDaniel Eklöf2021-06-24-0/+5
|
* changelog: composed -> combiningDaniel Eklöf2021-06-24-2/+2
|
* changelog: put emphasis on ‘opt-in’ as wellDaniel Eklöf2021-06-24-1/+1
|
* changelog: updates to “grapheme shaping”Daniel Eklöf2021-06-24-4/+9
|
* changelog: add a “grapheme shaping” sectionDaniel Eklöf2021-06-24-0/+53
|
* changelog: -Dterminfo-install-location meson command line optionDaniel Eklöf2021-06-23-0/+2
|
* changelog: add ref to #600 (-o,--override for footclient)Daniel Eklöf2021-06-23-1/+2
|
* wayland: apply CSD/SSD changes in the surface configure eventDaniel Eklöf2021-06-23-0/+1
| | | | | | | | | | | | | | | | | | The configure event asks the client to change its decoration mode. The configured state should not be applied immediately. Clients must send an ack_configure in response to this event. See xdg_surface.configure and xdg_surface.ack_configure for details. In particular, ”the configured state should *not* be applied immediately”. Instead, treat CSD/SSD changes like all other window dimension related changes: store the to-be mode in win->configure, and apply it in the surface configure event. This fixes an issue where foot incorrectly resized the window when the server switched between CSD/SSD at run-time.
* config: add csd.button-color optionDaniel Eklöf2021-06-20-0/+1
| | | | | | | | This option controls the foreground color of the minimize/maximize/close buttons. I.e. the color used to draw the minimize/maximize/close glyphs. It defaults to default background color.
* uri: hostname_is_localhost(): don’t crash if hostname == NULLDaniel Eklöf2021-06-19-0/+1
|
* render: use a timer instead of relying on the frame callback for title update throttlingDaniel Eklöf2021-06-18-0/+2
| | | | | | | | | | | | | | | | | | | | | Using the frame callback works most of the time, but e.g. Sway doesn’t call it while the window is hidden, and thus prevents us from updating the title in e.g. stacked views. This patch uses a timer FD instead. We store a timestamp from when the title was last updated. When the application wants to update the title, we first check if we already have a timer running, and if so, does nothing. If no timer is running, check the timestamp. If enough time has passed, update the title immediately. If not, instantiate a timer and wait for it to trigger. Set the minimum time between two updates to ~8ms (twice per frame, for a 60Hz output, and ~once per frame on a 120Hz output). Closes #591
* config: add underline-offset optionDaniel Eklöf2021-06-17-0/+2
| | | | | | | | This option allows the user to configure a custom underline offset. That is, use the user provided offset instead of the font provided one. Closes #490
* search: don’t crash when we don’t have any XKB compose stateDaniel Eklöf2021-06-16-0/+2
|
* csi: implement XTVERSION (CSI > 0q)Daniel Eklöf2021-06-13-0/+3
| | | | | | | | | | | | This is a fairly new XTerm extension. The reply is on the format: DCS > | text ST XTerm replies with ‘text’ = “XTerm(366)”. Foot replies with ‘text’ = “foot(1.6.4)” Closes #359
* Override options from command lineRyan Farley2021-06-12-0/+2
| | | | | | | | | Allow any configuration option to be overridden with -o/--override 'section.key=value' arguments, as suggested in #554 update completitions for override slight refactoring to ease footclient support
* config: demote “no configuration found, using defaults” to a mere warningDaniel Eklöf2021-06-10-0/+3
| | | | | And don’t notify the user in the terminal window, only log it on stderr.
* term: free the data associated with the pixman image when destroying box-drawing glyphsDaniel Eklöf2021-06-09-0/+3
| | | | Closes #586
* selection: add support for TEXT/STRING/UTF8_STRING mime-types in incoming offersDaniel Eklöf2021-06-09-0/+2
| | | | | | | | | We were already offering these mime types for our own clipboard data, but ignored them in incoming offers. Fixes paste issues from Geany. Closes #583
* Merge branch 'charset-shift-fixes'Craig Barnes2021-06-09-0/+4
|\
| * changelog: add issue links for previous 2 entriesCraig Barnes2021-06-09-2/+3
| |
| * vt: fix SS2/SS3 escape sequences to act correctly as single shiftsCraig Barnes2021-06-08-0/+2
| | | | | | | | | | | | These sequences are supposed to affect the next printable ASCII character and then reset to the previous character set, but before this commit they were behaving like locking shifts.
| * vt: add support for LS2 and LS3 locking shiftsCraig Barnes2021-06-08-0/+1
| |
* | sixel: add support for overlapping sixelsDaniel Eklöf2021-06-09-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Writing a sixel on top of an already existing sixel currently has the following limitations in foot: * The parts of the first sixel that is covered by the new sixel are removed, completely. Even if the new sixel has transparent areas. I.e. writing a transparent sixel on top of another sixel *replaces* the first sixel with the new sixel, instead of layering them on top of each other. * The second sixel erases the first sixel cell-wise. That is, a sixel whose size isn’t a multiple of the cell dimensions will leave unsightly holes in the first sixel. This patch takes care of both issues. The first one is actually the easiest one: all we need to do is calculate the intersection, and blend the two images. To keep things relatively simple, we use the pixman image from the *new* image, and use the ‘OVER_REVERSE’ operation to blend the new image over the old one. That is, the old image is still split into four tiles (top, left, right, bottom), just like before. But instead of throwing away the fifth middle tile, we blend it with the new image. As an optimization, this is only done if the new image has transparency (P1=1). The second problem is solved by detecting when we’re erasing an area from the second image that is larger than the new image. In this case, we enlarge the new image, and copy the old image into the new one. Finally, when we enlarge the new image, there may be areas in the new image that is *not* covered by the old image. These areas are made transparent. The end result is: * Each cell is covered by at *most* 1 sixel image. I.e. the total numbers of sixels are finite. This is important for the ‘mpv --vo=sixel’ use case - we don’t want to end up with thousands of sixels layered on top of each other. * Writing an opaque sixel on top of another sixel has _almost_ zero performance impact. Especially if the two sixels have the same size, so that we don’t have to resize the new image. Again, important for the ‘mpv --vo=sixel’ use case. Closes #562
* | changelog: tabs are preservedDaniel Eklöf2021-06-09-0/+2
|/
* csi: IL+DL: move cursor to column 0Daniel Eklöf2021-06-08-0/+1
| | | | | | | | | This fixes vttest 11.6.6.3 Test non-VT100 -> Test ISO-6429 colors -> Test of VT102-style features with BCE -> Test Insert/Delete Char/Line
* render: reverse video only swaps *default* fg/bgDaniel Eklöf2021-06-08-0/+3
| | | | | | | | | This matches XTerm behavior, and fixes vttest 11.6.6.2: Test non-VT100 -> Test ISO-6429 colors -> Test of VT102-style features with BCE -> Test of screen features
* input: pass through scrollback-* key bindings when alt screen is activwDaniel Eklöf2021-06-04-0/+3
| | | | | | | | | Since the alt screen have no scrollback, all scrollback-* actions are effectively no-ops when the alt screen is active. Make them available to the client application instead. Closes #573
* osc: implement iTerm2’s OSC-9 - desktop notificationsDaniel Eklöf2021-06-04-0/+1
|
* changelog: text reflow performanceDaniel Eklöf2021-06-04-0/+1
|
* slave/spawn: restore SIGHUP handler after fork(), before exec()Daniel Eklöf2021-06-02-0/+1
| | | | | | Foot installs a SIG_IGN handler for SIGHUP. Ignored signals are inherited in sub-processes. Thus, we need to restore it to SIG_DFL before exec:ing.
* grid: don’t cut multi-column chars in half when resizing the alt screenDaniel Eklöf2021-06-02-0/+2
| | | | | | | | When we resize the alt screen, we don’t reflow the text, we simply truncate all the lines. When doing this, make sure we don’t truncate in the middle of a multi-column character.
* url-mode: off-by-one error in end-point column of auto-detected URLsDaniel Eklöf2021-06-02-0/+2
| | | | | | When an auto-detected URL ended *on* the right-most column, the URL endpoint was off by one, resulting in the underline in URL mode being one character short.
* config: add boolean option tweak.pua-double-widthDaniel Eklöf2021-06-01-0/+3
| | | | | | | When enabled, PUA (Private Usage Area) codepoints are always treated as double-width glyphs, regardless of the actual glyph width. Requires allow-overflowing-double-width-glyphs=yes
* selection: pay attention to hard linebreaks when search for word boundariesDaniel Eklöf2021-05-31-0/+2
| | | | | | | | | | | | | | | | | | | Double-clicking on a word in the left or right margin, would line-wrap the selection if there was a non-empty cell in the corresponding right/left margin on the prev/next line. Regardless of whether there was a hard linebreak or not. Script to reprouce: !/bin/bash cols=$(tput cols) printf "%*coo\nbar\n" $((${cols} - 2)) f Run, then double click either “foo” or “bar”. Neither should select the other part. Closes #565
* changelog: add bug ref to ‘environment section added to foot/footclient’Daniel Eklöf2021-05-30-1/+2
|
* doc: add ENVIRONMENT section to foot(1) and footclient(1) man pagesCraig Barnes2021-05-30-0/+2
| | | | Closes #556
* config: add ‘include’ directiveDaniel Eklöf2021-05-28-0/+2
| | | | | | | | | | | | | | | This allows you to include sub-configurations. For example, theme files. The ‘include’ directive is a top-level keyword. I.e. it cannot be used inside sections. * The included file must be specified with an absolute path * The included file is parsed in its own scope * Nested includes are allowed * Multiple include directives are allowed Closes #555
* notify: add ${window-title}Daniel Eklöf2021-05-27-0/+1
|
* config: notify: change default value to use ${app-id}Daniel Eklöf2021-05-27-0/+2
| | | | | Make the default value of ‘notify’ use ${app-id} for icon and application name.
* term: fix crash when an OSC-8 URI wraps around the scrollbackDaniel Eklöf2021-05-26-0/+2
| | | | | | | | | | | | | | | | Long OSC-8 URIs, that are split up over multiple rows, are handled by emitting one URI range on each row the URL touches. This was done by initializing a row index variable, and then incrementing it each loop iteration. This caused an out-of-bounds array access when the row index reached the maximum number of scrollback lines. The fix is simple: make sure the row index variable wraps around, instead of incrementing without any bounds. Closes #552
* changelog: fixed mod+shift+tab regressionDaniel Eklöf2021-05-26-0/+3
|
* Merge branch 'ctrl-c-cancel'Craig Barnes2021-05-25-0/+1
|\
| * config: bind ctrl+c to "cancel" in search/url mode by defaultCraig Barnes2021-05-25-0/+1
| | | | | | | | Closes #544
* | wayland: roundtrip: log error and abort when wl_display_roundtrip() failsDaniel Eklöf2021-05-25-0/+3
|/ | | | | | | | | | | | | | | | | | | | ayl_roundtrip() has the following code: wl_display_roundtrip(wayl->display); while (wl_display_prepare_read(wayl->display) != 0) wl_display_dispatch_pending(wayl->display); wayl_flush(wayl); If the first wl_display_roundtrip() fails, for example because the Wayland socket has been closed, we may get stuck in the while-loop. This happens if the read queue isn’t empty, in which case wl_display_prepare_read() will return -1 and we’ll continue trying to dispatch the pending events forever, never succeeding since the socket is gone. Closes #542
* url-mode: remove overlapping URLs, not just duplicatesDaniel Eklöf2021-05-22-0/+1
| | | | | | | | | | | | | | | | | echo -e '\e]8;;https://www.foo.bar\e\\https://www.foo\e]8;;\e\\.bar' will produce an OSC-8 URL (https://www.foo) that is slightly shorter than the auto-detected one (https://www.foo.bar). This produces strange results in URL mode. For example, if url.osc8-underline=always, the OSC8 underline will be removed when url-mode is exited. This patch changes the behavior so that auto-detected URLs that overlap OSC-8 URLs are removed. Note that OSC-8 URLs cannot overlap with each other, and that auto-detected URLs also cannot overlap with each other.
* config: add url.protocolsDaniel Eklöf2021-05-22-0/+2
| | | | | | | This makes the protocols recognized by auto-detected URLs configurable. Closes #531
* config: move url-mode related options to a dedicated section, ‘url’Daniel Eklöf2021-05-22-3/+11
|