aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
* changelog: 1.7.01.7.0Daniel Eklöf2021-03-20-4/+3
|
* meson/pkgbuild: bump version to 1.7.0Daniel Eklöf2021-03-20-2/+2
|
* Merge branch 'add-bash-completions'Daniel Eklöf2021-03-17-0/+164
|\ | | | | | | Closes #10
| * Add: Bash completion for foot and footclientSimon Schricker2021-03-17-0/+164
|/ | | | | | | * use toe for terminfo, thanks Craig. * adds optional dependency on bash-completion for positional arguments Co-authored-by: Craig Barnes <craigbarnes@protonmail.com>
* Merge branch 'optimized-print-function'Daniel Eklöf2021-03-16-16/+95
|\
| * csi: update ASCII printer function pointer when switching to/from alt screenDaniel Eklöf2021-03-16-0/+1
| | | | | | | | | | This is necessary since switching screen may change how many sixels we have in the scrollback.
| * term: update_ascii_printer(): log when we (actually) switch printerDaniel Eklöf2021-03-16-1/+11
| |
| * term: runtime switch between a ‘fast’ and a ‘generic’ ASCII print functionDaniel Eklöf2021-03-16-16/+84
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | term_print() is called whenever the client application “prints” something to the grid. It is called for both ASCII and UTF-8 characters, and needs to handle sixels, insert mode and ASCII vs. graphical charsets. Since it’s on the hot path, this becomes unnecessarily slow. This patch adds a “fast” version of term_print(), tailored for the common case: ASCII characters in non-insert mode, without any sixels and non-graphical charsets. A new function, term_update_ascii_printer(), has been added, and must be called whenever: * The currently selected charset *index* changes * The currently selected charset changes (from ASCII to graphical, or vice verse) * Sixels are added to the grid * Sixels are removed from the grid * Insert mode is enabled/disabled
* | config: open_config(): remove unused argument ‘conf’Daniel Eklöf2021-03-16-2/+2
|/
* Merge branch 'term-print-assume-col-can-be-incremented'Daniel Eklöf2021-03-16-4/+4
|\
| * term: term_print(): assume we’re *not* at the right marginDaniel Eklöf2021-03-14-4/+4
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | That is, assume we can, and should, increment the cursor column. This changes the emitted assembly from: 518fb: 8b 8b f8 05 00 00 mov 0x5f8(%rbx),%ecx 51901: ff c9 dec %ecx 51903: 39 d1 cmp %edx,%ecx 51905: 7e 11 jle 51918 <term_print.constprop.0+0x78> 51907: ff c2 inc %edx 51909: 89 50 10 mov %edx,0x10(%rax) 5190c: 5b pop %rbx 5190d: 5d pop %rbp 5190e: 41 5c pop %r12 51910: c3 ret 51911: 0f 1f 80 00 00 00 00 nopl 0x0(%rax) 51918: c6 40 18 01 movb $0x1,0x18(%rax) 5191c: 5b pop %rbx 5191d: 5d pop %rbp 5191e: 41 5c pop %r12 51920: c3 ret To: 5191c: 41 8d 50 01 lea 0x1(%r8),%edx 51920: 89 50 10 mov %edx,0x10(%rax) 51923: 3b 93 f8 05 00 00 cmp 0x5f8(%rbx),%edx 51929: 0f 8d 21 01 00 00 jge 51a50 <term_print.constprop.0+0x190> 5192f: 5b pop %rbx 51930: 5d pop %rbp 51931: 41 5c pop %r12 51933: c3 ret ... 51a50: c6 40 18 01 movb $0x1,0x18(%rax) 51a54: 44 89 40 10 mov %r8d,0x10(%rax) 51a58: 5b pop %rbx 51a59: 5d pop %rbp 51a5a: 41 5c pop %r12 51a5c: c3 ret I.e. it cuts the normal path from 10 instructions down to 8. It increases the "bad" path with one extra instruction.
* sixel: sixel_overwrite_at_cursor(): early exit when the image list is emptyDaniel Eklöf2021-03-14-0/+3
| | | | | | | | This avoids a call to sixel_overwrite_by_row() (where we also exit early if the image list is empty). This saves a couple of instructions to set up the arguments for sixel_overwrite_by_row().
* Merge branch 'sixel-fix-max-geometry'Daniel Eklöf2021-03-14-2/+4
|\
| * sixel: max geometry should be max geometry, not current window sizeDaniel Eklöf2021-03-14-2/+4
| | | | | | | | | | | | | | | | | | “current geometry” will report whatever value is the smallest; the max geometry or the current window size. But “max geometry” always returns the configured max geometry. This aligns foot’s behavior with XTerm.
* | Merge branch 'option-no-wait'Daniel Eklöf2021-03-14-41/+114
|\ \ | |/ |/| | | Closes #395
| * add changelog entry, completions and man entry for -N, --no-waitFelipe Trzaskowski2021-03-13-0/+8
| |
| * fix code style issues and memory leakFelipe Trzaskowski2021-03-13-13/+8
| |
| * add option to detach the client process from the terminal instanceFelipe Trzaskowski2021-03-13-42/+112
| |
* | scripts: generate-alt-random: reduce number of emitted sixelsDaniel Eklöf2021-03-14-1/+1
| | | | | | | | | | | | After emitting multiple color bands for each sixel row, the increased amount of sixel data shifted the balance in the profiling data, causing a performance regression in regular ASCII handling.
* | Merge branch 'drain-pty-when-client-terminates'Daniel Eklöf2021-03-13-10/+3
|\ \ | |/ |/|
| * term: don’t close PTY when client application diesDaniel Eklöf2021-03-12-10/+3
|/ | | | | | | | | Closing it as soon as we detect that the client has died, means we may not have drained it completely. The PTY is either closed _by_ the client application, or by us when we shutdown the terminal. Thus, leaving it open (until we call term_shutdown()) is fine.
* client: repair usage outputDaniel Eklöf2021-03-12-2/+2
|
* client: remove excess ‘-’ from ‘--log-level’ in usageDaniel Eklöf2021-03-12-1/+1
|
* changelog: sixel decoding performance improvementsDaniel Eklöf2021-03-12-0/+1
|
* Merge branch 'sixel-background-and-transparency'Daniel Eklöf2021-03-12-50/+98
|\ | | | | | | Closes #391
| * changelog: implemented DCS parameter P2Daniel Eklöf2021-03-11-0/+5
| |
| * render: sixels: render cursor, if it’s partially covered by an opaque sixelDaniel Eklöf2021-03-11-1/+3
| |
| * sixel: implement P2=1 - transparent pixelsDaniel Eklöf2021-03-11-50/+91
|/ | | | | | | | | | | | | | | | | | | | | | | | When P2=1, empty pixels are transparent. This patch also changes the behavior of P2=0|2, from setting empty pixels to the default background color, to instead use the *current* background color. To implement this, a couple of changes are needed: * Sixel pixels always use alpha=1.0, except for *empty* cells when P2=1 (i.e. transparent pixels). * The renderer draws sixels with the OVER operator, instead of the SRC operator. * The renderer *must* now render the cells beneath the sixel. As an optimization, this is only done for sixels where P2=1. I.e. for fully opaque sixels, there’s no need to render the cells beneath. The sixel renderer isn’t yet hooked into the multi-threaded renderer. This means *rows* (not just the cells) beneath maybe-transparent sixels are rendered single-threaded. Closes #391.
* Merge branch 'sixel-optimize'Daniel Eklöf2021-03-11-64/+217
|\
| * changelog: empty pixel rows at the bottom of a sixel is now trimmedDaniel Eklöf2021-03-11-0/+1
| |
| * sixel: decgra: set max-non-empty-row-no when resizing the imageDaniel Eklöf2021-03-11-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | This ensures we don’t trim off bottom rows in unhook(). This could happen either because the application used “Set Raster Attributes” to configure an image size larger than the sixels later emitted. Or, the last sixel row contains empty pixel rows. In either case, the size set with “Set Raster Attributes” defines the *minimum* image size; the image may still end up being larger.
| * generate-alt-random: sixel: emit at least 4 color bandsDaniel Eklöf2021-03-11-1/+1
| | | | | | | | | | | | This fixes an issue where there was a relatively high chance of not emitting any color bands at all, causing the final image size to be too small.
| * generate-alt-random: DECGRI: don’t emit zero-length repeat sequencesDaniel Eklöf2021-03-11-3/+3
| |
| * generate-alt-random: DECGRI: random repeat lengthsDaniel Eklöf2021-03-11-1/+5
| |
| * generate-alt-random: don’t skip that last partial rowDaniel Eklöf2021-03-11-2/+3
| |
| * generate-alt-random: emit “Set Raster Attributes” before color definitionsDaniel Eklöf2021-03-11-4/+4
| |
| * generate-alt-random: 50% chance of overwriting the last sixelDaniel Eklöf2021-03-11-6/+14
| |
| * generate-alt-random: emit sixels on the alt screenDaniel Eklöf2021-03-11-2/+5
| |
| * generate-alt-random: emit multiple sixel bandsDaniel Eklöf2021-03-11-10/+17
| | | | | | | | This ensures we’re getting the ‘$’ command PGO:d
| * sixel: decgri: handle a repeat count of 0, by ignoring itDaniel Eklöf2021-03-11-2/+11
| |
| * generate-alt-random: sixel: pan/pad must not be 0Daniel Eklöf2021-03-11-1/+1
| |
| * sixel: add: add sixel_add_many(), improving performance of DECGRIDaniel Eklöf2021-03-11-24/+27
| | | | | | | | | | | | | | | | | | | | | | DECGRI, i.e. repeat sixel character, only need to do image resizing, and updating the current ‘column’ value *once*. By adding sixel_add_many(), and doing the size/resize checking there, the performance of sixel_add() is made much simpler. This boosts performance quite noticeably when the application is emitting many and/or long repeat sequences.
| * sixel: add: calculate absolute row no inside the loopDaniel Eklöf2021-03-11-2/+3
| | | | | | | | | | | | This results in the same number of instructions inside the loop, with a ‘lea’ instead of a ‘mov’, but simplifies the post-loop logic to update the global state.
| * sixel: add: increase data pointer instead of offsetDaniel Eklöf2021-03-11-3/+3
| | | | | | | | | | Same ‘add’ instruction to increase the offset, but simpler ‘mov’ instruction when writing the pixel data.
| * sixel: decgri: avoid load inside for-loopDaniel Eklöf2021-03-11-1/+2
| |
| * sixel: add optimized resize_horizontally() and resize_vertically()Daniel Eklöf2021-03-11-2/+78
| | | | | | | | | | The resize operations performed in the “hot” path either change the width, or the height, but not both at the same time.
| * sixel: empty pixels in the last sixel row doesn’t contribute to the image heightDaniel Eklöf2021-03-11-1/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | All-empty pixels rows in the last sixel row should not be included in the final sixel image. This allows applications to emit sixels whose height is not a multiple of 6, and is how XTerm works. This is done by tracking the largest row number that contains non-empty pixels. In unhook, when emitting the image, the image height is adjusted based on this value.
| * sixel: resize: width is no longer a multiple of 6Daniel Eklöf2021-03-11-16/+4
| |
| * sixel: set ‘col’ outside image boundaries when we’ve reached max heightDaniel Eklöf2021-03-11-3/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This is to optimize sixel_add(). It already checks ‘pos’, to see if it needs to resize the image, and if the resize fails (either due to allocation failures, or because we’ve reached the maximum width), we bail out. We need to do the same thing for height. But, we don’t want to add another check to sixel_add() since its’s performance critical. By setting ‘col’ outside the image boundaries when ‘row’ reaches the maximum image height, we can “re-use” the existing code in sixel_add().
| * sixel: remove ‘max_col’Daniel Eklöf2021-03-11-13/+3
| | | | | | | | The image width *is* the maximum number of columns we’ve seen.
| * sixel: adjust image height when processing ‘-’Daniel Eklöf2021-03-11-8/+8
| |
| * sixel: resize: check new width/height against max geometry earlyDaniel Eklöf2021-03-11-9/+9
| |
| * Revert "sixel: resize: always round up height to a multiple of 6"Daniel Eklöf2021-03-11-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 5a9d70da837c20a9641d6cbadccc962a8e5a4283. This broke jexer. Comparing with what XTerm does, we can see that it updates its image height for *each* pixel in *each* sixel. I.e. empty pixels at the bottom of a sixel will not increase the image size. Foot currently bumps the image height 6 pixels at a time, i.e. always a whole pixel. Given this, always rounding up the height to the nearest multiple of 6 (say, for example, when responding to a DECGRA command), is wrong. Now, we use the image size specified in DECGRA as is, while still allowing the image to grow beyond that if necessary. What’s left to do, if we want to behave *exactly* like XTerm, is stop growing the image with 6 pixels at a time when dynamically adjusting the image size.
| * sixel: add: use de-reference the term struct for each access to the backing imageDaniel Eklöf2021-03-11-7/+10
| |
| * sixel: get rid of an ‘imul’ in sixel_add()Daniel Eklöf2021-03-11-2/+5
| | | | | | | | | | | | | | | | By storing the current row’s byte offset into the backing image in the terminal struct. This replaces the ‘imul’ with a load, which can potentially be slow. But, this data should already be in the cache.
| * sixel: add: resize is already checking against the current max geometryDaniel Eklöf2021-03-11-6/+0
| |
| * sixel: resize: don’t resize beyond the current max geometryDaniel Eklöf2021-03-11-0/+14
| |
| * sixel: unhook: make sure image height is within boundsDaniel Eklöf2021-03-11-0/+4
| | | | | | | | | | | | | | | | When we allocate the backing buffer, the number of allocated rows is a multiple of 6. When persisting the image, make sure its height does not exceed the current maximum height.
| * scripts: generate-alt-random: sixel: emit DECGRI - Repeat CharacterDaniel Eklöf2021-03-11-5/+6
| |
| * sixel: add: simplify check for resize neededDaniel Eklöf2021-03-11-1/+1
| | | | | | | | | | Since the image height is always a multiple of 6, there’s no need to round up the image height.
| * sixel: resize: always round up height to a multiple of 6Daniel Eklöf2021-03-11-6/+4
| | | | | | | | Sixels are always a multiple of six.
| * sixel: fixup row is multiple of 6Daniel Eklöf2021-03-11-1/+1
| |
| * sixel: calculate alpha when updating the paletteDaniel Eklöf2021-03-11-9/+6
| | | | | | | | | | Calculate color, with alpha, when updating the palette instead of every time we *use* the palette.
| * sixel: pre-calculate color before calling sixel_add()Daniel Eklöf2021-03-11-3/+11
| | | | | | | | | | This improves performance of DECGRI, since we now only need to calculate the color once for the entire repeat sequence.
| * sixel: ignore invalid sixel characters in DECGRI (repeat)Daniel Eklöf2021-03-11-1/+11
| |
| * sixel: avoid multiplication inside the inner sixel emitter loopDaniel Eklöf2021-03-11-6/+6
| |
| * sixel: store current row position in pixels, not charactersDaniel Eklöf2021-03-11-6/+5
|/
* meson: SOURCE_DIR is not a valid macro in custom_target()Daniel Eklöf2021-03-11-1/+1
| | | | | | | But appears to have been allowed in older versions of meson. Fixes an issue where foot’s version was always reported as the last stable release, even though it was a git build.
* Merge branch 'consume-modifiers-for-client-application'Daniel Eklöf2021-03-08-7/+28
|\ | | | | | | Closes #376
| * keymap: handle shift+tab combos correctly, after consuming modifiersDaniel Eklöf2021-03-08-2/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Shift+Tab is an odd bird in XKB; it produces a shifted variant of tab, ISO_Left_Tab, with Shift being a consumed modifier. From a terminal perspective, Tab and ISO_Left_Tab are the same key, with Shift+Tab generating ‘CSI Z’, and all other combos generating a ‘CSI 27;mods;9~’ escape. Before, when we didn’t filter out consumed modifiers, we could simply re-use the keymap for Tab when translating ISO_Left_Tab. This is no longer possible, since shift has been filtered out. As a result, Shift+Tab no longer generated ‘CSI Z’, but ‘\t’. I.e as if shift wasn’t being pressed. This patch adds a separate keymap table for ISO_Left_Tab. It’s MOD_ANY entry corresponds to Shift+Tab, and emits ‘CSI Z’. All its other entries *exclude* shift (since it has been consumed), *but*, the encoded modifier (in the escape sequences) *include* shift.
| * input: do not include consumed modifiers in the set sent to the clientDaniel Eklöf2021-03-08-5/+7
|/ | | | | | | When sending a key escape sequence to the client application, do not include consumed modifiers. Fixes part of #376
* Merge branch 'xkbcommon-bump'Daniel Eklöf2021-03-08-1/+3
|\ | | | | | | Closes #389
| * meson: bump minimum xkbcommon version to 1.0.0Craig Barnes2021-03-07-1/+3
|/ | | | | | | This requirement is due to the recently added maybe_repair_key_combo() function, which is making use of xkb_keymap_key_get_mods_for_level(). See also: commit a5b554761a8b376657be2a7e613b37fd5803920c.
* sixel: size provided by DECGRA does *not* limit the sixel sizeDaniel Eklöf2021-03-06-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Foot has, up until now, used a fixed image size when the application used DECGRA (Raster Attributes) to “configure” the image size. This was based on a misunderstanding, that this was how you emitted sixels where the height was *not* a multiple of 6. This isn’t the case. The VT340 documentation is actually pretty clear about this: Ph and Pv do not limit the size of the image defined by the sixel data. However, Ph and Pv let you omit background sixel data from the image definition and still have a color background. They also provide a concise way for the application or terminal to encode the size of an image. This is also how XTerm behaves. Test image: \EPq "1;1;1;1 #0;2;0;0;0#1;2;100;100;0#2;2;0;100;0 #1~~@@vv@@~~@@~~$ #2??}}GG}}??}}??- #1!14@ \E\ This uses DECGRA to set the image size to 1x1. The sixel however is *not* clipped to 1x1, but is resized to 14x12
* url-mode: fix auto-detection of URLs in the top corner of the viewportDaniel Eklöf2021-03-06-4/+4
| | | | | | | | | | | | | | | | The ‘proto_chars’ variable is kind of like a FIFO, where characters from the grid is pushed to the back of it. I.e. the last <n> bytes are at the *end* of the array. This was what the protocol matching logic expected. However, it was only true after reading ‘max_prot_len’ characters from the grid. Before that, the last <n> bytes from the grid was in the *beginning* of ‘proto_chars’. This meant we did not detect URLs starting in the top left corner of the viewport. Test case: foot sh -c "echo http://test.com && sleep 9999"
* Merge branch 'consume-modifiers-for-key-bindings'Daniel Eklöf2021-03-04-71/+273
|\ | | | | | | Closes #376
| * changelog: new key binding matching logicDaniel Eklöf2021-03-04-0/+4
| |
| * url-mode: ignore keys with modifiersDaniel Eklöf2021-03-04-0/+3
| |
| * foot.ini: lower case Shift+X default bindingsDaniel Eklöf2021-03-04-6/+6
| |
| * input: repair key combos containing both explicit modifier and shifted symbolDaniel Eklöf2021-03-04-6/+125
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If a user-provided key combo contains both an explicit modifier, and the shifted symbol it produces, replace the symbol with its un-shifted version. Example: Control+Shift+U contains both ‘Shift’, and ‘U’, where ‘Shift’ is the modifier that shifts ‘u’ to ‘U’. Such modifiers are “consumed”, i.e. filtered out, when matching key combos. As such, Control+Shift+U will never trigger since we’ll never be able to match the consumed modifier ‘Shift’. The above combo can be written in two ways: - Control+U - Control+Shift+u To be able to detect that Control+Shift+U is an invalid combination, we need to check all *shifted* symbols for all key *codes*. Once we’ve detected a shifted symbol (and where it differs from the un-shifted symbol), we loop all modifier sets that produce the shift level where our shifted symbol is. For each such set, check if it intersects with the user-provided key combo’s modifier set. If there is an intersection, it means the user provided a key combo containing a modifier and symbol, such that the modifier is consumed when the symbol is produced. In this case, we replace the symbol with its un-shifted version.
| * config: parse_key_combos: lower case manually, instead of calling tolower()Daniel Eklöf2021-03-04-1/+1
| | | | | | | | tolower() is locale dependent, something we do not want in this case.
| * doc: foot.ini: update default key bindings - use lower case keysDaniel Eklöf2021-03-04-7/+7
| |
| * config: fix default key binding for extend-to-next-whitespaceDaniel Eklöf2021-03-04-1/+1
| | | | | | | | Bindings now use lower-cased keys
| * doc: foot.ini: key combos must *not* include shift and be in upper caseDaniel Eklöf2021-03-04-3/+3
| |
| * input: rewrite of how we match foot’s own key bindingsDaniel Eklöf2021-03-04-42/+117
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bindings are matched in one out of three ways: * By translated (by XKB) symbols * By untranslated symbols * By raw key codes A translated symbol is affected by pressed modifiers, some of which can be “consumed”. Consumed modifiers to not partake in the comparison with the binding’s modifiers. In this mode, ctrl+shift+2 maps to ctrl+@ on a US layout. Untranslated symbols, or un-shifted symbols refer to the “base” symbol of the pressed key, i.e. it’s unaffected by modifiers. In this mode, consumed modifiers *do* partake in the comparison with the binding’s modifiers, and ctrl+shift+2 maps to ctrl+shift+2 on a US layout. More examples: ctrl+shift+u maps to ctrl+U in the translated lookup, while ctrl+shift+u maps to ctrl+shift+u in the untranslated lookup. Finally, we also match raw key codes. This allows our bindings to work using the same physical keys when the user switches between latin and non-latin layouts. This means key bindings in foot.ini *must* not include both +shift+ and a *shifted* key. I.e. ctrl+shift+U is not a valid combo as it cannot be triggered. Unfortunately, this was how you were supposed to write bindings up until now... so, we try to detect such bindings, log a deprecation warning and then “fix” the binding for the user. When specifying bindings in foot.ini, both ctrl+U and ctrl+shift+u are valid, and will work. The latter is preferred though, since we cannot detect the raw key code for the former variant. Personally, I also prefer the latter one because it is more explicit; it’s more obvious which keys are involved. However, in some cases it makes more sense to use the other variant. Typically for non-letter combos.
| * input: ask XKB for consumed modifiers, but don’t actually use them just yetDaniel Eklöf2021-03-04-10/+11
|/
* Revert "url-mode: ignore keys with modifiers"Daniel Eklöf2021-03-04-3/+0
| | | | | | | This reverts commit e5cd09bf3f3b78b408052688645321e99ae2dc5e. This needs to be applied on the consume-modifiers-for-key-bindings branch.
* Merge branch 'ime-dont-commit-unless-we-have-ime-focus'Daniel Eklöf2021-03-04-0/+12
|\ | | | | | | Closes #384
| * ime: don’t commit IME changes when we don’t have IME focusDaniel Eklöf2021-03-02-0/+12
| | | | | | | | | | | | | | | | | | Fixes log spamming in Sway: 00:54:07.780 [DEBUG] [wlr] [types/wlr_text_input_v3.c:181] Text input commit received without focus 00:54:07.780 [INFO] [sway/input/text_input.c:127] Inactive text input tried to commit an update Closes #384
* | input: mutter has been seen sending NULL surfaces in pointer enterDaniel Eklöf2021-03-04-0/+5
| |
* | input: exit URLs mode on mouse button eventsDaniel Eklöf2021-03-04-0/+1
| | | | | | | | This makes URLs mode behave like scrollback search mode.
* | render: jump-labels: case insensitive comparison when looking for matching keysDaniel Eklöf2021-03-04-1/+1
| |
* | url-mode: ignore keys with modifiersDaniel Eklöf2021-03-04-0/+3
| |
* | changelog: oops, vertical-letter-offset is new in 1.7.xDaniel Eklöf2021-03-02-1/+0
| | | | | | | | | | No need to a changelog entry for fixing something that hasn’t yet been released.
* | Merge branch 'fix-vertical-letter-offset-config'Daniel Eklöf2021-03-02-1/+3
|\ \ | |/ |/|
| * Mention fix in Changelog.L3MON4D32021-03-01-0/+2
| |
| * Fix typo.L3MON4D32021-03-01-1/+1
| |
* | Merge branch 'add-name-section-to-foot-ctlseq'Daniel Eklöf2021-03-01-0/+3
|\ \ | |/ |/|
| * Add NAME section to foot-ctlseqs.7; fixes whatis entry for manual page.Felix Lechner2021-02-28-0/+3
|/ | | | | | | | In a recent Debian build from master, Lintian complained about a bad whatis entry for this manual page. The tag description [1] says a NAME section is required. It is added here. [1] https://lintian.debian.org/tags/bad-whatis-entry.html
* Merge branch 'sixel-private-mode-80-scrolling'Daniel Eklöf2021-02-27-41/+75
|\ | | | | | | Closes #361