This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-05
Channels
- # announcements (1)
- # asami (21)
- # aws (19)
- # babashka (37)
- # beginners (38)
- # clj-kondo (7)
- # clj-otel (8)
- # clojure (29)
- # clojure-europe (54)
- # clojure-nl (3)
- # clojure-spec (2)
- # clojure-uk (2)
- # clojurescript (15)
- # conjure (1)
- # data-science (1)
- # datomic (21)
- # emacs (6)
- # events (3)
- # figwheel-main (1)
- # gratitude (13)
- # holy-lambda (11)
- # joyride (6)
- # klipse (3)
- # malli (14)
- # missionary (26)
- # nbb (31)
- # omni-trace (2)
- # pathom (3)
- # reagent (1)
- # reitit (1)
- # releases (1)
- # shadow-cljs (24)
- # sql (27)
- # tools-deps (4)
- # vim (21)
hi bob!
haven't gotten there yet 😅
indeed 😄
@borkdude thank you for tweeting about editor = emacs -Q
- my life has gotten a lot better 😄
Morning!
gudd morning
Mornin'
Any vim or nvim users here?
I’m seeing a bunch of annoying characters when piping stuff into nvim
(and even less
). Like so:
git help branch |nvim
GIT-BRANCH(1) Git Manual GIT-BRANCH(1)
NNAAMMEE
git-branch - List, create, or delete branches
SSYYNNOOPPSSIISS
_g_i_t _b_r_a_n_c_h [--color[=<when>] | --no-color] [--show-current]
[-v [--abbrev=<n> | --no-abbrev]]
... and so on
its to do with the highlighting and making things bold etc in man pages than to do with nvim/vim. try git help branch | col -b | nvim
col -b
would remove all the weird stuff you're not supposed to see as a visible char 😄
thanks a bunch, @U7ERLH6JX! I wonder if there’s a vim/nvim setting that can do something similar, so that I can just have it in my .vimrc
(or whatever the nvim equivalent is)
The col -b
invocation also seems a bit arcane for removing text decoration :face_with_monocle:
omg… the explanation for bolding with ^H
is so interesting
The effect you're seeing here is called overstruck characters and it comes from the days when computers would be connected to line printers rather than screens. Man pages were created early in the Unix days and are typeset with a program named nroff (which has roots that predate even Unix) that uses these sequences to encode its text decorations, even to this day.
So one way to make text bold (or, print it stronger) was to print a letter, back out one space, then print it again. In your example, N^HNA^HAM^HME^HE is being used to print the word NAME in bold.
Hm, the +MANPAGER
option is not available in Neovim. Too bad.
@U0AQ3HP9U try nvim +Man
not +MANPAGER
?
Doesn’t work either @U7ERLH6JX
¯\(ツ)/¯
export MANPAGER='nvim +Man!'
seems to work
then do git help branch
or some other man cmd
or git help branch | nvim +Man! -
ahhhh you’re right! Thank you so much, @U7ERLH6JX!
Why use anything Less than Vim 😅
yeah when in (n)vim, unix pipe your way out of your problems 😉
i didnt use it for manpages this way til now, mostly ran :Man foo
from nvim
I’m going for the export
in a .bash
file, because why not.
I usually only visit nvim briefly, like a ninja in the night
I know you can live there, but I haven’t dared
well its more than that for me now, part of my identity almost 😛
have this whole curated, <20ms startup, clojure biased lua conf now 😎
When it comes to text editing in nvim, I’m the most knowledgable person that I know of, and I apply that knowledge wherever I can (shoving vim into whatever orifices other applications will allow me to, or, better, showing other stuff into vim)
But I’ve been scared off of using an editor as more than an editor
Or, well, enough that I haven’t bothered making the effort yet
check out https://github.com/lispyclouds/dotfiles if that serves as a staring point 😛 WARNING: bit opinionated
It’s also to do with portability. I like using close to bare bones stuff, so that I can do the same on pretty much any other unix env that my fingers happen upon.
Looks interesting, though 🙂
I tried installing yabai, but had no luck, even with concerted effort. (That’s also a reason I haven’t dared; I’m really tired of spending time trying to fix config/install issues. I just want to work, with stuff that just works 🙂 )
yeah i too like the bare bones stuff too, kept the "text editing" bit same for nvim. vim. vi. difference starts showing up when you open some code file 😛
its a massive time suck (hey, time wasted enjoying isnt wasted 😛 ) but quite like the fact that after a while its pretty much an extension of your brain, not much thinking
hm, it’s not pasting everything. E.g. the line with synopsis is like so: