feature request - make hardcopy print text properties

Hi all, How easy would it be to extend the hardcopy command to also print any attached text properties? I'm asking because I have a file in which I've underlined various words in the buffer using text properties and would like to print the end result. Syntax highlighting is not an option because a word might be highlighted in one place but not in other places. I've also tried TOhtml but it doesn't do it either. -mike -- -- 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 http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/118vanv%24n81%241%40ciao.gmane.io.

Re: No error with ]s when nowrapscan?

On Tue, 22 Sept 2026 at 22:42, Tim Chase <vim@tim.thechases.com> wrote:

On 2026-09-22 22:06, Doug Kearns wrote:
> >   $ vim one.txt two.txt three.txt
> >   :set hidden nowrapscan
> >
> > I then repeatedly issued
> >
> >   :try | exec 'norm ]s' | catch | n | endtry
> >
> > (using @: then subsequently @@ makes this easy) which worked for
> > finding all the misspelled words in the *first* file, but after
> > finding the last one in that file, the ]s *should* fail because
> > there is no "next" bad-spelling in the current file and wrapscan is
> > off.  So it seems like the ]s *should* have thrown an exception, get
> > caught, and then go to the :next file instead where the process can
> > repeat.  But it seems to silently swallow the "no more bad spellings
> > in the current file" without letting me catch the condition.
[snip]
> You could leverage temporary use of `:set debug=beep`.

A promising proposition, but I'm not sure that's working for me?

I tried the your suggestion with each of

  debug=beep
  debug=throw
  debug=throw,beep

but none of them change the behavior of the ]s (not) throwing an error
to get caught.  I do see "Beep!" text at the bottom of my screen when I
expect the exception/catch, but no catchable error seems to happen.

Yes, I was thinking you could test for that text calling execute().  I also forgot there's an assert_beeps() but you'd probably want to save restore v:errors.

Perhaps just checking for a change in cursor position is good enough?

Regards,

Doug [not in a dev environment]

--
--
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 http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CAJ1uvoBK3VZrh-FM1qBEtMnCcAdXGKnBK%2B1QKJLsteZgy_FmZw%40mail.gmail.com.

Re: No error with ]s when nowrapscan?

On 2026-09-22 22:06, Doug Kearns wrote: > > $ vim one.txt two.txt three.txt > > :set hidden nowrapscan > > > > I then repeatedly issued > > > > :try | exec 'norm ]s' | catch | n | endtry > > > > (using @: then subsequently @@ makes this easy) which worked for > > finding all the misspelled words in the *first* file, but after > > finding the last one in that file, the ]s *should* fail because > > there is no "next" bad-spelling in the current file and wrapscan is > > off. So it seems like the ]s *should* have thrown an exception, get > > caught, and then go to the :next file instead where the process can > > repeat. But it seems to silently swallow the "no more bad spellings > > in the current file" without letting me catch the condition. [snip] > You could leverage temporary use of `:set debug=beep`. A promising proposition, but I'm not sure that's working for me? I tried the your suggestion with each of debug=beep debug=throw debug=throw,beep but none of them change the behavior of the ]s (not) throwing an error to get caught. I do see "Beep!" text at the bottom of my screen when I expect the exception/catch, but no catchable error seems to happen. -tim -- -- -- 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 http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/arJ3qtqAZvkO2pNO%40thechases.com.

Re: No error with ]s when nowrapscan?

Hi Tim,

On Tue, 22 Sept 2026 at 03:25, Tim Chase <vim@tim.thechases.com> wrote:

Playing with something recently, I discovered that ]s doesn't seem to
throw any sort of error when wrapscan is off and it hits the end of the
file.

To demonstrate with the following setup (where {one,two,three}.txt are
some files with a couple misspelled words scattered throughout each)

  $ vim one.txt two.txt three.txt
  :set hidden nowrapscan

I then repeatedly issued

  :try | exec 'norm ]s' | catch | n | endtry

(using @: then subsequently @@ makes this easy) which worked for finding
all the misspelled words in the *first* file, but after finding the
last one in that file, the ]s *should* fail because there is no "next"
bad-spelling in the current file and wrapscan is off.  So it seems like
the ]s *should* have thrown an exception, get caught, and then go to
the :next file instead where the process can repeat.  But it seems to
silently swallow the "no more bad spellings in the current file" without
letting me catch the condition.

AFAICT there's no

  :spellnext

type ex command or spellnext() function corresponding to ]s that might
be more error-cooperative.

Is there a better way to go about this? 

You could leverage temporary use of `:set debug=beep`.

Regards,

Doug 

--
--
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 http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vim_use/CAJ1uvoC%3DwuKB3u3kA4%3D4Hp1LHSoiK%3De-cz44ts79kyXeSt9R0g%40mail.gmail.com.

No error with ]s when nowrapscan?

Playing with something recently, I discovered that ]s doesn't seem to throw any sort of error when wrapscan is off and it hits the end of the file. To demonstrate with the following setup (where {one,two,three}.txt are some files with a couple misspelled words scattered throughout each) $ vim one.txt two.txt three.txt :set hidden nowrapscan I then repeatedly issued :try | exec 'norm ]s' | catch | n | endtry (using @: then subsequently @@ makes this easy) which worked for finding all the misspelled words in the *first* file, but after finding the last one in that file, the ]s *should* fail because there is no "next" bad-spelling in the current file and wrapscan is off. So it seems like the ]s *should* have thrown an exception, get caught, and then go to the :next file instead where the process can repeat. But it seems to silently swallow the "no more bad spellings in the current file" without letting me catch the condition. AFAICT there's no :spellnext type ex command or spellnext() function corresponding to ]s that might be more error-cooperative. Is there a better way to go about this? -tim -- -- -- 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 http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/arFobflska4lvgtE%40thechases.com.

Re: timer_start to refresh rulerformat

and then it worked, after update I guess to vim 9.2 (including patch 1-1011) \o/ thank you. -- -- 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 http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/14308c5f-ff74-4430-9d91-9d221b9888f8%40sfr.fr.

Re: ShellCmdPre autocommand ?

hello, On Mon, Sep 07, 2026 at 05:30:56PM -0700, Maxim Kim wrote: > What about  > :!<CTRL-R><CTRL-f> ? worth to mention but something like :r!dpkg -r <cfile> is reusable from history so you can type it once and use it repeatedly and <cfile> updated. not only :r!dpkg -r $c is faster to type and less error prone but as it is a environment variable, I can use it it a custom script. I can also imagine exporting more informations like getline(), line(), col() ... anyway: I never use <c-r><c-f> but it's worth to mention the <c-r>* during the talk. Thank you! -- Marc Chantreux ☎ 03.68.85.60.79 -- -- 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 http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/vim_use/ap-aW3-HCOwXGhX-%40prometheus.