On Mon, 7 Dec 2020 at 02:29, Tim Chase wrote:
>
> On 2020-12-06 20:23, Tim Chase wrote:
> > They're ugly, but vim will at least let you do them.
>
> Oh, one other caveat: it only finds the bookends and starts the next
> search after the closing bookend. So if there is the possiblity that
> the
Felipe wasn't the one complaining, he was showing a good colorization
example.
On Monday, December 7, 2020 at 10:11:14 AM UTC-5 stevelitt wrote:
> On Wed, 2 Dec 2020 16:33:13 -0800 (PST)
> Felipe Contreras wrote:
>
> >
> > This is how asciidoc markdown looks on my side with my colorscheme:
> >
On Wed, 2 Dec 2020 16:33:13 -0800 (PST)
Felipe Contreras wrote:
>
> This is how asciidoc markdown looks on my side with my colorscheme:
>
> https://snipboard.io/jDiaJK.jpg
>
> Cheers.
>
I've seen worse.
SteveT
Steve Litt
Autumn 2020 featured book: Thriving in Tough Times
Hi all,
I sometimes need to change the encoding used for a file. I have the
default set to latin1 except for files with an ucs-bom. However, when
I load a file encoded in UTF-8 or CP-437 the default is wrong. What I
do then is normally to ":set fencs=utf8" and ":vi" to reload the file.
On Mon, Dec 7, 2020 at 5:40 PM A. Wik wrote:
>
> Hi all,
>
> I sometimes need to change the encoding used for a file. I have the
> default set to latin1 except for files with an ucs-bom. However, when
> I load a file encoded in UTF-8 or CP-437 the default is wrong. What I
> do then is normally
Hello Vimmers,
when multiple plugins are placed inside the opt directory of a package,
all this plugins will be shown as completions for the :packadd command.
E.g. I have created a package called LSP. Inside this package, there are
three optional plugins (vim-lsp, asyncomplete-lsp and
The actual "correct" way to "change" the encoding of a buffer is, I
believe, with the "++enc" option, added either to :e (e.g. `:e
++enc=utf8`) or several similar commands such as indeed :vi (`:vi
++enc=utf8`).
However I couldn't find a way to make it work with a file-less buffer,
such as
On 06/12/2020 19.07, 'Paul' via vim_use wrote:
I'm not sure what was meant by "work within the nth tab separated field",
I believe he means by using nth-tab fields as motions or text objects.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below
Ah yes, I had also tried passing "-" as a filename for the reload
attempts, nope, it was interpreted as an actual "-" file name...
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit
