summaryrefslogtreecommitdiffstats
path: root/sys/teken/teken_subr.h
Commit message (Collapse)AuthorAgeFilesLines
* Properly use the cursor to bound the position for CUP.ed2011-10-101-1/+1
| | | | | | | We must take the origin region into account when clamping the cursor position. MFC after: 3 days
* Tab should not blank cells.ed2011-10-071-14/+1
| | | | | | | | | | | | It seems I was under the impression that a tab differs from a single forward tabulation, namely that it blanks the underlying cells. This seems not to be the case. They are identical. This should fix applications like jove(1) that use tabs instead of explicit cursor position setting. Reported by: Brett Glass <brett lariat net> MFC after: 3 days, after it's tested
* Fix various whitespace inconsistencies in sys/teken.ed2011-06-261-2/+2
|
* Use proper bounds checking on VPA.ed2010-12-051-2/+1
| | | | | | | | We must check against tp->t_cursor.tp_row, not row, to figure out whether we must clamp the cursor position. Submitted by: luigi MFC after: 3 weeks
* Make ^L with cons25 and origin mode bit more sane.ed2010-08-091-3/+9
| | | | | | | | Even though cons25 normally doesn't support origin regions, this emulator does allow you to do it. It makes more sense to blank only the origin region when emitting ^L instead of blanking the entire screen. Apart from that, we should always place the cursor inside the origin region, which doesn't happen right now.
* Allow Syscons terminal emulators to provide function key strings.ed2009-11-111-2/+2
| | | | | | | | | xterm and cons25 have some incompatibilities when it comes to escape sequences for special keys, such as F1 to F12, home, end, etc. Add a new te_fkeystr() that can be used to override the strings. scterm-sck won't do anything with this, but scterm-teken will use teken_get_sequences() to obtain the proper sequence.
* Always home the cursor when changing the scrolling region.ed2009-11-111-7/+8
| | | | | | | | | | I thought this only had to be done when in origin mode, to ensure that the cursor is not placed outside the origin, but it seems this is also done when not in origin mode. This fixes some artifacts when pressing ^L while running irssi in tmux. (Almost) nobody noticed this, because cons25 doesn't have scrolling regions.
* Discard Device Control Strings and Operating System Commands.ed2009-10-081-3/+15
| | | | | | | | | | | | | | These strings often contain things like: - Window titles. - Extended key map functionality. - Color palette switching. We could look at these features in the future (if people consider them to be important enough), but we'd better discard them now. This fixes some artifacts people reported when using TERM=xterm. Reported by: des@, Paul B. Mahol
* Add support for VT200-style mouse input.ed2009-09-271-0/+6
| | | | | | | | | | | | | | | | | | | Right now if applications want to use the mouse on the command line, they use sysmouse(4) and install a signal handler in the kernel to deliver signals when mouse events arrive. This conflicts with my plan to change to TERM=xterm, so implement proper VT200-style mouse input. Because mouse input is now streamed through the TTY, it means you can now SSH to another system on the console and use the mouse there as well. The disadvantage of the VT200 mouse protocol, is that it doesn't seem to generate events when moving the cursor. Only when pressing and releasing mouse buttons. There are different protocols as well, but this one seems to be most commonly supported. Reported by: Paul B. Mahol <onemda gmail com> Tested with: vim(1)
* Add 256 color support.ed2009-09-261-0/+32
| | | | | | | | | | | | | | It is quite inconvenient that if an application for xterm uses 256 color mode, text suddenly starts to blink (because of ;5; in the middle). We'd better just implement 256 color mode and add a conversion routine from 256 to 8 color mode, which doesn't seem to be too bad in practice. Remapping colors is done quite simple. If one of the channels is most actively represented, primary colors are used. If two channels are most actively represented, secondary colors are used. If all three channels are equal (gray), it picks between black and white. Reported by: Paul B. Mahol <onemda gmail com>
* Properly get out of origin mode if the cursor has to move outside of it.ed2009-09-261-3/+12
| | | | | | | | | | | | | In some cases events may occur that move the cursor outside the scrolling region while in origin mode, which is normally not possible. Events like these include: - Alignment test. - Restore cursor. Properly switch off origin mode in these cases. MFC after: 1 month
* Get rid of now deprecated SCS wrappers.ed2009-09-261-11/+11
| | | | | We always build SCS, even when processing 8-bit data. There is no reason why we should be able to disable it now.
* Conformance: ignore {delete,insert} line while outside the scrolling region.ed2009-09-251-0/+10
| | | | | | | | | | | | | I noticed a small inconsistency in delete and insert line between xterm and libteken. libteken allows these actions to happen while the cursor is placed outside the scrolling region, while xterm does not. This behaviour seems to be VT100-like. Confirmation: http://www.vt100.net/docs/vt102-ug/chapter5.html "This sequence is ignored when cursor is outside scrolling region." MFC after: 1 month
* Make SCS work in 8-bit mode.ed2009-09-241-1/+2
| | | | | | | | | | | | | | | | | | | | | | | This means we can finally do things like VT100 box drawing when using Syscons (8-bit characters). As far as I know, the only remaining issue is the absense of proper escape sequences for special keyboard characters (cursor, F1 to F12, etc) and xterm emulation should be ready for general use. Enabling xterm would have the following advantages: - Easier possible migration to Unicode. cons25 termcap entries are very 8-bit centric. They use things like CP437 characters for box drawing, etc. - Better support for SSH'ing to other operating systems/devices. Most switches use VT100-style admin interfaces. - Reduced bandwidth, because applications can now use things like scrolling regions. - You can finally use applications like dtach(1) on both the console and inside an xterm.
* Commit all local modifications I have to libteken:ed2009-09-121-58/+70
| | | | | | | | - Make xterm/cons25 support runtime configurable. This allows me to share libteken between syscons and my new vt driver. - Add a fix to print blanks after printing a double width character to prevent rendering artifacts. - Add some more utility functions that I use in the vt driver.
* Make 8-bit support run-time configurable.ed2009-09-121-6/+13
| | | | | Now to do the same for xterm support. This means people can eventually toy around with xterm+UTF-8 without recompiling their kernel.
* Make resizing of teken terminals a bit more safe.ed2009-09-121-0/+3
| | | | | | Just perform a full reset when resizing the terminal. This means the cursor, scrolling region, etc. are never positioned outside the terminal.
* Move libteken out of the syscons directory.ed2009-09-031-0/+1209
I initially committed libteken to sys/dev/syscons/teken, but now that I'm working on a console driver myself, I noticed this was not a good decision. Move it to sys/teken to make it easier for other drivers to use a terminal emulator. Also list teken.c in sys/conf/files, instead of listing it in all the files.arch files separately.
OpenPOWER on IntegriCloud