

If you choose to give Fedora a try, I recommend Ultramarine, which has more set up from the start, including their “Terrs” repository with more updated packages.
If you choose to give Fedora a try, I recommend Ultramarine, which has more set up from the start, including their “Terrs” repository with more updated packages.
Ah yes you can tell by the post title:
best linux terminal emulator
For me: Wezterm. It does pretty much everything. I don’t think Alacritty/Kitty etc. offer anything over it for my usage, and the developer is a pleasure to engage with.
Second place is Konsole – it does a lot, is easy to configure, and obviously integrates nicely with KDE apps.
Honorable mention is Extraterm, which has been working on cool features for a long time, and is now Qt based.
I suggest trying this one for Zsh, over the more common one: https://github.com/zdharma-continuum/fast-syntax-highlighting
As someone else said, setting less’ jump value is helpful.
Another tool I use, mostly for the zshall manpage, is https://github.com/kristopolous/mansnip
No, that’s not used by Zsh.
Glad you have it working. This may also work:
_stfu () {
shift words
(( CURRENT-=1 ))
_normal -P
}
compdef _stfu stfu
FWIW I’ve read an Arch dev complain that folks using any 3rd party installer are not in fact “running Arch” and should not claim to be doing so.
The window shade problem is keeping me from Wayland. AFAIU there’s currently no commitment to ever fix it on Wayland, it’s only a maybe.
For anyone interested, it’s being tracked here.
So . . . not relevant to my comment?
OK, I see some differences between your two screenshots, but what’s the relevance to my comment?
I don’t know what I should be noticing there. I can’t see any text for the tool buttons along the left edge of the window.
I have trouble with both, but more experience with GIMP. I can’t stand all the little tool buttons with no text. I want the name of each tool always visible on its button.
I have the same problem with Inkscape.
Ooh I haven’t seen this one. Anyone have a comment on this vs the KleverNotes project? I think that’s the name.
Thanks again for posting your improvements! I will have them!
The idea here, checking for newline characters rather than counting lines, is to prevent it treating one line that is so long it wraps to the next as counting as a multiline input, right? So now I’m looking like
EDIT: lemmy is at least mangling ampersands here. Hard to believe it doesn’t have proper code blocks yet…
# -- Run input if single line, otherwise insert newline --
# Key: enter
# Assumes: setopt interactivecomments
# Credit: https://programming.dev/comment/2479198
.zle_accept-except-multiline () {
if [[ $BUFFER != *$'\n'* ]] {
zle accept-line
return
} else {
zle self-insert-unmeta
if [[ $BUFFER == *$'\n'*$'\n'* ]] {
local hint="# Use alt+enter to submit this multiline input"
if [[ $BUFFER != *${hint}* ]] {
LBUFFER+=$hint
zle self-insert-unmeta
}
}
}
}
zle -N .zle_accept-except-multiline
bindkey '^M' .zle_accept-except-multiline # Enter
# -- Run input if multiline, otherwise insert newline --
# Key: alt+enter
# Credit: https://programming.dev/comment/2479198
.zle_accept_only_multiline () {
if [[ $BUFFER == *$'\n'* ]] {
zle accept-line
} else {
zle self-insert-unmeta
}
}
zle -N .zle_accept_only_multiline
bindkey '^[^M' .zle_accept_only_multiline # Enter
For pushing the line/multiline, I combine it with my clear function (ctrl+l):
# -- Refresh prompt, rerunning any hooks --
# Credit: romkatv/z4h
.zle_redraw-prompt () {
for 1 ( chpwd $chpwd_functions precmd $precmd_functions ) {
if (( $+functions[$1] )) $1 &>/dev/null
}
zle .reset-prompt
zle -R
}
# -- Better Screen Clearing --
# Clear line and redraw prompt, restore line at next prompt
# Key: ctrl+l
# Depends: .zle_redraw-prompt
.zle_push-line-and-clear () { zle push-input; zle clear-screen; .zle_redraw-prompt }
zle -N .zle_push-line-and-clear
bindkey '^L' .zle_push-line-and-clear # ctrl+l
I started using this, it makes a lot of sense and I like it, thanks!
I can imagine myself forgetting how to accept multiline input with alt+enter, so I added a help message to _zle_ml_enter
in the multiline case after the second line. It assumes setopt interactivecomments
is already set:
EDIT: note that lemmy mangles the less-than symbol
# -- Run input if single line, otherwise insert newline --
# Key: enter
# Assumes: setopt interactivecomments
# Credit: https://programming.dev/comment/2479198
.zle_accept-except-multiline () {
if (( BUFFERLINES <= 1 )) {
zle accept-line
} else {
zle self-insert-unmeta
if (( BUFFERLINES == 2 )) {
LBUFFER+="# Use alt+enter to submit this multiline input"
zle self-insert-unmeta
}
}
}
zle -N .zle_accept-except-multiline
bindkey '^M' .zle_accept-except-multiline # Enter
I hope I’m not annoying anyone, but it’s ado.
It’s been a while, but my clumsy adding of a comment to the buffer is unnecessary, given
zle -M
, which will display a message outside of the buffer. So here’s an updated version:# -- Run input if single line, otherwise insert newline -- # Key: enter # Credit: https://programming.dev/comment/2479198 .zle_accept-except-multiline () { if [[ $BUFFER != *$'\n'* ]] { zle .accept-line return } else { zle .self-insert-unmeta zle -M 'Use alt+enter to submit this multiline input' } } zle -N .zle_accept-except-multiline bindkey '^M' .zle_accept-except-multiline # Enter # -- Run input if multiline, otherwise insert newline -- # Key: alt+enter # Credit: https://programming.dev/comment/2479198 .zle_accept-only-multiline () { if [[ $BUFFER == *$'\n'* ]] { zle .accept-line } else { zle .self-insert-unmeta } } zle -N .zle_accept-only-multiline bindkey '^[^M' .zle_accept-only-multiline # Enter