Go Mono
from there rather than installing it from the #OpenBSD repo. Adding this to my .Xresources
and voila I have the Go Mono font and symbols.xterm*faceName: Go Mono Nerd Font Mono#RunBSD
xterm*renderFont: true
xterm*faceSize: 10
Go Mono
from there rather than installing it from the #OpenBSD repo. Adding this to my .Xresources
and voila I have the Go Mono font and symbols.xterm*faceName: Go Mono Nerd Font Mono#RunBSD
xterm*renderFont: true
xterm*faceSize: 10
sixel
in xterm
or the kitty protocol in kitty
, I've decided to stick with good old #Xterm . Also on my #FreeBSD daily driver I'm used to such luxuries as icons in the terminal like font awesome or nerd fonts but even though I could have used alacritty
or kitty
to achieve this I have decided to for go them. After all what do they do other make it look pretty ? I don't get any other functionality from them and they can easily be replaced with text. You might have noticed too that although I'm a #Wayland chic on my #ThinkPad I've decided to be all nostalgic and stick with Xorg on OpenBSD. I haven't yet settled on a window manager be it tiling or stacking but #HerbstluftWM and #Openbox are in my sights although I'm still using the default #Fvwm right now. I have my Qutebrowser setup and aerc for my email. Printing via cups and xsane for scanning. Looking into nsxiv
for an image viewer as the OpenBSD port of imv
is well out of date. Yes I'm having to make small changes but once I'm finished this wee Dell Optiplex 3080 tower will be perfect for daily driving OpenBSD and I'm looking forward to learning lots more. #RunBSDXterm doesnt display text - please answear #xterm
One item I *haven't* configured yet in `xterm` is URL handling. In the brief time I used the `foot` terminal on Wayland I liked how they manage URLs by assigning a keycode that underlines all the URLs and assigns a key sequence to each to use to open the URL in the browser:
https://codeberg.org/dnkl/foot#urls
I wonder if something like this could be configured in tmux? If so, that would make this feature independent of whatever terminal is in use.
Day 07 of #31DaysOfFreeBSD :freebsd:
Had some real fun exploring `xterm(1)` and getting my terminal configured nicely in `~/.Xresources` with the Nord color palette and Fira Code font! This is a config that I can carry with me for use in any X environment on BSD or Linux:
https://gitlab.com/dwarmstrong/dotfiles/-/blob/master/.Xresources?ref_type=heads
As I'm configuring `xterm` today, I learned that the program predates X!
Source: https://invisible-island.net/xterm/xterm.faq.html#who_did_it
What could #sixel support specifically entail that could be impacted by pledge()? #xterm is still only drawing pixels into pixmaps, sixel mode or otherwise.
Unwillingness to turn on a new (since 2013) not-very-well-tested-until-recently feature, almost certainly. NetBSD delayed turning it on until 2020. (Debian went straight for turning it on in 2013, by contrast.) But I don't see how pledge() would have had any hand in the decision.
my #xterm bores me. About time to fiddle with xterm*cursorOnTime and xterm*cursorOffTime
Sí ya sé, no es viernes...
#viernesdeescritorio
#desktopfriday
#twm
#xterm
#openbsd76
Aprender a valorar lo simple de la vida jaja!!
Xterm, esa terminal que seguro tienes por ahí pero que nunca valoras...
Apparently #Alpine booted fine with #ZFS and Wiki pages are helpful. It also still comes with ifconfig for network configuration which I love. However, well there seems always to be a HOWEVER follows, after I installed #Xorg and #xterm, testing X seemed like worked but my keyboard was not working under X. It worked in tty but as soon as I stated X with startx, keyboard became unresponsive while touchpad was working. I cannot even switched to tty because keyboard was not working at all. Doing a pill X in ssh session stopped X and keyboard still worked under tty. Have to try fix this. 2/2
@HydrePrever : Il en faut deux : #xterm pour les trucs sérieux et #tilda pour le fun