Rebbe Malachi: February 2025

Friday, February 28, 2025

Sorry For Top Posting

Sorry for top posting on my recent response. My email does not allow bottom posting.

Re: Getting Gvim print button to print in landscape mode

I tried it and unfortunately get the same results. It always prints in portrait mode regardless of the setting. The only way I can get it to print in landscape is by using the print dialogue and selecting landscape there.

Get Outlook for iOS

From: vim_use@googlegroups.com <vim_use@googlegroups.com> on behalf of Eric Marceau <eajmarceau@gmail.com>
Sent: Friday, February 28, 2025 5:11:25 PM
To: vim_use@googlegroups.com <vim_use@googlegroups.com>
Subject: Getting Gvim print button to print in landscape mode

Hello,

I've tried to set my vimrc parameters for landscape mode. Here is what I have in my file:

"###
"######    Hardcopy Options
"######   See:   https://vimdoc.sourceforge.net/htmldoc/print.html#print-options
"######   See:   https://vimdoc.sourceforge.net/htmldoc/options.html#'statusline' for header format
"###

"###    Specify font for printout
"set printmbcharset="default"
"set printoptions="paper:letter,portrait:n,duplex:off,left:5pc,right:5pc,top:5pc,bottom:5pc,syntax:n,wrap:y"
"set printoptions="portrait:n,duplex:off,wrap:y,syntax:n"
"set printoptions="portrait:n,numbers:y,wrap:y,syntax:n,left:5pc,right:5pc,top:5pc,bottom:5pc"
"set printoptions="portrait:n,numbers:y,wrap:y,syntax:y"
set printoptions="portrait:n"
"set printfont="Courier:h15"
set printfont="SourceSans:h15"
"#set printheader="%t%=%{strftime('%c')}%=Page %N"
set printheader="%<%f%=Page %N"

The line in bold is, in my view, set to force landscape, but that never happens. As you can see, I tried many variations before eliminating everything, but the orientation for the printoptions variable.

Can someone tell me

why not getting what I want with what is currently in the vimrc?
what I need to change to make a vimrc-specified setting control the print format to give me what I want?

Thank you.

$ vim --version

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Feb 03 2025 11:54:38)
Included patches: 1-16, 647, 17-579, 1969, 580-647, 678, 648-1848, 4975, 5016, 5023, 5072, 2068, 1849-1854, 1857, 1855-1857, 1331, 1858, 1858-1859, 1873, 1860-1969, 1992, 1970-1992, 2010, 1993-2068, 2106, 2069-2106, 2108, 2107-2109, 2109-3995, 4563, 4646, 4774, 4895, 4899, 4901, 4919, 213, 1840, 1846-1847, 2110-2112, 2121
Modified by team+vim@tracker.debian.org
Compiled by team+vim@tracker.debian.org
Huge version with GTK3 GUI. Features included (+) or not (-):
+acl               +file_in_path      +mouse_urxvt       -tag_any_white
+arabic            +find_in_path      +mouse_xterm       +tcl
+autocmd           +float             +multi_byte        +termguicolors
+autochdir         +folding           +multi_lang        +terminal
-autoservername    -footer            -mzscheme          +terminfo
+balloon_eval      +fork()            +netbeans_intg     +termresponse
+balloon_eval_term +gettext           +num64             +textobjects
+browse            -hangul_input      +packages          +textprop
++builtin_terms    +iconv             +path_extra        +timers
+byte_offset       +insert_expand     +perl              +title
+channel           +ipv6              +persistent_undo   +toolbar
+cindent           +job               +popupwin          +user_commands
+clientserver      +jumplist          +postscript        +vartabs
+clipboard         +keymap            +printer           +vertsplit
+cmdline_compl     +lambda            +profile           +vim9script
+cmdline_hist      +langmap           -python            +viminfo
+cmdline_info      +libcall           +python3           +virtualedit
+comments          +linebreak         +quickfix          +visual
+conceal           +lispindent        +reltime           +visualextra
+cryptv            +listcmds          +rightleft         +vreplace
+cscope            +localmap          +ruby              +wildignore
+cursorbind        +lua               +scrollbind        +wildmenu
+cursorshape       +menu              +signs             +windows
+dialog_con_gui    +mksession         +smartindent       +writebackup
+diff              +modify_fname      +sodium            +X11
+digraphs          +mouse             +sound             -xfontset
+dnd               +mouseshape        +spell             +xim
-ebcdic            +mouse_dec         +startuptime       +xpm
+emacs_tags        +mouse_gpm         +statusline        +xsmp_interact
+eval              -mouse_jsbterm     -sun_workshop      +xterm_clipboard
+ex_extra          +mouse_netterm     +syntax            -xterm_save
+extra_search      +mouse_sgr         +tag_binary
-farsi             -mouse_sysmouse    -tag_old_static
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
2nd user gvimrc file: "~/.vim/gvimrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
    system menu file: "$VIMRUNTIME/menu.vim"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wdate-time -g -O2 -ffile-prefix-map=/build/vim-q7BeVl/vim-8.2.3995=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: gcc -L. -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -fstack-protector-strong -rdynamic -Wl,-export-dynamic -Wl,-E -Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -lharfbuzz -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE -lm -ltinfo -lselinux -lcanberra -lsodium -lacl -lattr -lgpm -L/usr/lib -llua5.2 -Wl,-E -fstack-protector-strong -L/usr/local/lib -L/usr/lib/x86_64-linux-gnu/perl/5.34/CORE -lperl -ldl -lm -lpthread -lcrypt -L/usr/lib/python3.10/config-3.10-x86_64-linux-gnu -lpython3.10 -lcrypt -ldl -lm -lm -L/usr/lib/x86_64-linux-gnu -ltcl8.6 -ldl -lz -lpthread -lm -lruby-3.0 -lm -L/usr/lib

--
--
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/2723495e-770e-4479-8a1b-83ed7682fe21%40gmail.com.

Getting Gvim print button to print in landscape mode

Hello,

I've tried to set my vimrc parameters for landscape mode. Here is what I have in my file:

"###
"######    Hardcopy Options
"######   See:   https://vimdoc.sourceforge.net/htmldoc/print.html#print-options
"######   See:   https://vimdoc.sourceforge.net/htmldoc/options.html#'statusline' for header format
"###

"###    Specify font for printout
"set printmbcharset="default"
"set printoptions="paper:letter,portrait:n,duplex:off,left:5pc,right:5pc,top:5pc,bottom:5pc,syntax:n,wrap:y"
"set printoptions="portrait:n,duplex:off,wrap:y,syntax:n"
"set printoptions="portrait:n,numbers:y,wrap:y,syntax:n,left:5pc,right:5pc,top:5pc,bottom:5pc"
"set printoptions="portrait:n,numbers:y,wrap:y,syntax:y"
set printoptions="portrait:n"
"set printfont="Courier:h15"
set printfont="SourceSans:h15"
"#set printheader="%t%=%{strftime('%c')}%=Page %N"
set printheader="%<%f%=Page %N"

Can someone tell me

why not getting what I want with what is currently in the vimrc?
what I need to change to make a vimrc-specified setting control the print format to give me what I want?

Thank you.

$ vim --version

Thursday, February 27, 2025

Re: question about :term

hey this works -- thanx Enno!

On Thu, Feb 27, 2025 at 2:32 PM Enno <enno.nagel@gmail.com> wrote:

Good evening,

I am indeed unsure what the exact problem is, but it seems something like `nnoremap <silent> Q :<c-u>buffer #<bar>bdelete #<CR>` to keep the current buffer's window open might help;
that's a recurrent demand that has been addressed by many plug-ins such as https://github.com/mhinz/vim-sayonara

Enno

Le mercredi 26 février 2025 à 23:37:35 UTC+1, tooth pik a écrit :
when i have an edit session open in gvim, then start a :term inside that window, start a script running in the :term, then toggle back to the edit portion of the window to continue editing -- if in that edit session i edit another module i can't figure out how to quit the secondary edit without closing the whole edit window -- i tried :q, :bd, and they both end all editing and leave me with a whole window of :term

how can i quit that secondary edit and return to the first one?

sorry if i've explained this poorly

--
--
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/3bf77651-78fc-4b32-ae7a-566d18fef5d4n%40googlegroups.com.

Re: question about :term

Good evening,

I am indeed unsure what the exact problem is, but it seems something like `nnoremap <silent> Q :<c-u>buffer #<bar>bdelete #<CR>` to keep the current buffer's window open might help;

that's a recurrent demand that has been addressed by many plug-ins such as https://github.com/mhinz/vim-sayonara

Enno

Le mercredi 26 février 2025 à 23:37:35 UTC+1, tooth pik a écrit :

when i have an edit session open in gvim, then start a :term inside that window, start a script running in the :term, then toggle back to the edit portion of the window to continue editing -- if in that edit session i edit another module i can't figure out how to quit the secondary edit without closing the whole edit window -- i tried :q, :bd, and they both end all editing and leave me with a whole window of :term

how can i quit that secondary edit and return to the first one?

sorry if i've explained this poorly

Wednesday, February 26, 2025

Re: Unexpected indentation with :left

On Wed, Feb 26, 2025 at 7:44 PM Tim Chase <vim@tim.thechases.com> wrote:

The gist of my question/hope was wanting to get the N in

:left N

to prepend N *indents* (using N tabs if 'noet' and N*shiftwidth if 'et'
is set)

As it currently stands, with 'et' set, I get N spaces, not N
'shiftwidth', and if I have 'noet' set, I get int(N/tabstop) tabs
followed by mod(N, tabstop) spaces. E.g.

:set ts=8 sw=4

with

:set et
:'<,'>left 10

puts 10 spaces at the beginning of each trimmed line.

And without 'et' set:

:set noet
:'<,'>left 10

gives me one tab (8-worth) followed by 2 spaces.

Neither gives me 10 tabstops or 10 shiftwidths which is what I'd
expected.

-tim

This seemed like it might be useful, so I wrote it:

# Different from regular :left in that the indent is taken to be a multiple of the &shiftwidth setting and not just a number of spaces.
export def g:LeftIndentLines( line1: number, line2: number, indent: string )
var indentSize: number = indent == '' ? 0 : str2nr( indent )

if ( indentSize > 0 )
# Replace existing indent with the number of spaces required
execute $':{line1},{line2}s/^\s*/{repeat(" ", indentSize * &shiftwidth)}'

# Use retab to insert tabs if tab-based indentation is enabled3
execute $':{line1},{line2}retab!'
else
execute $':{line1},{line2}left'
endif
enddef
com! -nargs=? -range Left g:LeftIndentLines( <line1>, <line2>, <q-args> )

Call just like the regular :left, except with :Left. Takes a range and an indent (default is 0, just like regular :left). The only difference between this and the built in version is that the number passed to this is seen as a multiple of the shiftwidth instead of an absolute number of spaces. It will also call `retab!` to convert indents to tabs as needed.

Re: Unexpected indentation with :left

On 2025-02-26 10:31, D. Ben Knoble wrote:
> On Tuesday, February 25, 2025 at 7:10:46???PM UTC-5 Tim Chase wrote:
>>> Sets the indent in the lines to [indent] (default 0).
>>
>> indenting with N spaces rather than respecting 'shiftwidth' and 'expandtab'
>> [snip]
>> Is there a way to get the indent-count parameter of `:left` to behave
>> like using the > motion (which respects 'shiftwidth' and 'expandtab')?
>
> It took me a while to figure out what the question was, but I think you
> could something like this:
>
> V<motions>:left N | *retab!

The gist of my question/hope was wanting to get the N in

:left N

to prepend N *indents* (using N tabs if 'noet' and N*shiftwidth if 'et'
is set)

As it currently stands, with 'et' set, I get N spaces, not N
'shiftwidth', and if I have 'noet' set, I get int(N/tabstop) tabs
followed by mod(N, tabstop) spaces. E.g.

:set ts=8 sw=4

with

:set et
:'<,'>left 10

puts 10 spaces at the beginning of each trimmed line.

And without 'et' set:

:set noet
:'<,'>left 10

gives me one tab (8-worth) followed by 2 spaces.

Neither gives me 10 tabstops or 10 shiftwidths which is what I'd
expected.

-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/Z7-1hYLwzJ6SYKmO%40thechases.com.

Re: Difficulty using vim within xfce4-terminal

Yes, mouse support is enabled, and that's the way I want it! (mouse=a). As I noted, this works fine in xterm, but when used in xfce4-terminal, it does not.

On Monday, February 24, 2025 at 6:12:26 PM UTC-8 Grant Taylor wrote:

On 2/24/25 6:43 PM, Mark Waggoner wrote:
> Any advice?

I don't know if this is the case for you or not, but it almost sounds
like mouse support has been enabled in vim.

Try running `:set` and looking to see if mouse is set to anything.

I routinely run `:set mouse=` w/o any parameter to disable vim's
integrated mouse support.

Maybe it will help you get back to what you're used to.

--
Grant. . . .

question about :term

when i have an edit session open in gvim, then start a :term inside that window, start a script running in the :term, then toggle back to the edit portion of the window to continue editing -- if in that edit session i edit another module i can't figure out how to quit the secondary edit without closing the whole edit window -- i tried :q, :bd, and they both end all editing and leave me with a whole window of :term

how can i quit that secondary edit and return to the first one?

sorry if i've explained this poorly

Re: Unexpected indentation with :left

On Tuesday, February 25, 2025 at 7:10:46 PM UTC-5 Tim Chase wrote:

Reading the help for :left, it says:

Sets the indent in the lines to [indent] (default 0).

However, it seems to do that indenting with N spaces rather than
respecting 'shiftwidth' and 'expandtab' settings.

[snip]

Is there a way to get the indent-count parameter of `:left` to behave
like using the > motion (which respects 'shiftwidth' and 'expandtab')?

-tim

brought to my attention by this Reddit thread:
https://www.reddit.com/r/vim/comments/1ixcyt5/put_all_lines_in_visual_bloc_on_the_same_indent/

It took me a while to figure out what the question was, but I think you could something like this:

V<motions>:left N | *retab!

You'll probably have to adjust N above if you want to use tabs (so 3 indents with tab stops of 8 would be 24; I'm not sure if tabstop or softtabstop is what matters here).

Tuesday, February 25, 2025

Unexpected indentation with :left

Reading the help for :left, it says:

Sets the indent in the lines to [indent] (default 0).

However, it seems to do that indenting with N spaces rather than
respecting 'shiftwidth' and 'expandtab' settings.

Or do I just need to roll an independent solution? It's not as simple
as using

:{range}>>>>

because `:left` first removes all left-indentation before indenting.

The best I've been able to come up with is

:{range}le | {range}>>>>

With cpo-star in the default and using a linewise-visual-range, that
simplifies a bit to

:'<,'>le|*>>>>

While kinda-opaque, it does the Right Thing(tm)

Is there a way to get the indent-count parameter of `:left` to behave
like using the > motion (which respects 'shiftwidth' and 'expandtab')?

-tim

brought to my attention by this Reddit thread:
https://www.reddit.com/r/vim/comments/1ixcyt5/put_all_lines_in_visual_bloc_on_the_same_indent/

--

--
--
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/Z75b-2K2myS_L09M%40thechases.com.

Monday, February 24, 2025

Re: Difficulty using vim within xfce4-terminal

On 2/24/25 6:43 PM, Mark Waggoner wrote:
> Any advice?

I don't know if this is the case for you or not, but it almost sounds
like mouse support has been enabled in vim.

Try running `:set` and looking to see if mouse is set to anything.

I routinely run `:set mouse=` w/o any parameter to disable vim's
integrated mouse support.

Maybe it will help you get back to what you're used to.

--
Grant. . . .

--
--
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/1d6298db-9513-49d7-b135-cd96276f3e6b%40spamtrap.tnetconsulting.net.

Difficulty using vim within xfce4-terminal

I recently started using xfce4-terminal, and have found that if I run vim in that terminal vim is unable to own the x selection as evidenced by the highlighting during visual selection. Instead of reverse video, it is grey'd text. It is also evidenced by the fact that despite having things set up to automatically copy the visual selection to the clipboard, the selected value is no longer available for pasting if vim is suspended or exited.

Works fine from good old xterm, but I'd like it to work in xfce4-terminal as well.

Any advice?

vim version;

VIM - Vi IMproved 9.1 (2024 Jan 02)
Included patches: 1-836

Wednesday, February 12, 2025

Re: Is there a command line way to run gvim with a #ccffff color background?

how to unsubscribe?

пн, 10 февр. 2025 г. в 15:47, Chainsaw <chainsaw@fourbarlinkage.net>:

On Sunday, Feb 09, 2025 at 10:31 PM
Steve Litt <slitt@troubleshooters.com> wrote:

> Tony Mechelynck said on Mon, 10 Feb 2025 02:50:04 +0100
>
> >On Sun, Feb 9, 2025 at 9:39 PM <chainsaw@fourbarlinkage.net> wrote:
> >>
> >> On Sunday, Feb 09, 2025 at 03:28 PM
> >> Steve Litt <slitt@troubleshooters.com> wrote:
> >>
> >> > Is there a command line way to run gvim with a #ccffff color
> >> > background?
> >> >
> >> > Thanks
> >> >
> >> > SteveT
> >> >
> >> > Steve Litt
> >> > http://444domains.com
> >> >
> >>
> >>
> >> :highlight Normal guibg=#ccffff
> >
> >To run it always with that background, add the above line to your
> >vimrc.
> >
> >To do it once, run either
> > gvim --cmd "hi Normal guibg=#ccffff"
> >or
> > gvim -c "hi Normal guibg=#ccffff"
>
>
> Thanks Tony and Chainsaw. This is what I needed, and I put it in my
> menu.
>
> SteveT
>
> Steve Litt
>
> http://444domains.com
>

Here is another way triggered after loading a/any color scheme.

Say you want this to happen when you change to dracula colorcsheme:

augroup ColorschemeTweak
autocmd!
autocmd ColorScheme dracula highlight Normal guibg=#ccffff
augroup END

Or for any colorscheme:

augroup ColorschemeTweak
autocmd!
autocmd ColorScheme * highlight Normal guibg=#ccffff
augroup END

--
--
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/20250210084729.000014a4%40fourbarlinkage.net.

Monday, February 10, 2025

Re: Is there a command line way to run gvim with a #ccffff color background?

On Sunday, Feb 09, 2025 at 10:31 PM
Steve Litt <slitt@troubleshooters.com> wrote:

> Tony Mechelynck said on Mon, 10 Feb 2025 02:50:04 +0100
>
> >On Sun, Feb 9, 2025 at 9:39 PM <chainsaw@fourbarlinkage.net> wrote:
> >>
> >> On Sunday, Feb 09, 2025 at 03:28 PM
> >> Steve Litt <slitt@troubleshooters.com> wrote:
> >>
> >> > Is there a command line way to run gvim with a #ccffff color
> >> > background?
> >> >
> >> > Thanks
> >> >
> >> > SteveT
> >> >
> >> > Steve Litt
> >> > http://444domains.com
> >> >
> >>
> >>
> >> :highlight Normal guibg=#ccffff
> >
> >To run it always with that background, add the above line to your
> >vimrc.
> >
> >To do it once, run either
> > gvim --cmd "hi Normal guibg=#ccffff"
> >or
> > gvim -c "hi Normal guibg=#ccffff"
>
>
> Thanks Tony and Chainsaw. This is what I needed, and I put it in my
> menu.
>
> SteveT
>
> Steve Litt
>
> http://444domains.com
>

Here is another way triggered after loading a/any color scheme.

Say you want this to happen when you change to dracula colorcsheme:

augroup ColorschemeTweak
autocmd!
autocmd ColorScheme dracula highlight Normal guibg=#ccffff
augroup END

Or for any colorscheme:

augroup ColorschemeTweak
autocmd!
autocmd ColorScheme * highlight Normal guibg=#ccffff
augroup END

--
--
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/20250210084729.000014a4%40fourbarlinkage.net.

Sunday, February 9, 2025

Re: Is there a command line way to run gvim with a #ccffff color background?

Tony Mechelynck said on Mon, 10 Feb 2025 02:50:04 +0100

>On Sun, Feb 9, 2025 at 9:39 PM <chainsaw@fourbarlinkage.net> wrote:
>>
>> On Sunday, Feb 09, 2025 at 03:28 PM
>> Steve Litt <slitt@troubleshooters.com> wrote:
>>
>> > Is there a command line way to run gvim with a #ccffff color
>> > background?
>> >
>> > Thanks
>> >
>> > SteveT
>> >
>> > Steve Litt
>> > http://444domains.com
>> >
>>
>>
>> :highlight Normal guibg=#ccffff
>
>To run it always with that background, add the above line to your
>vimrc.
>
>To do it once, run either
> gvim --cmd "hi Normal guibg=#ccffff"
>or
> gvim -c "hi Normal guibg=#ccffff"

Thanks Tony and Chainsaw. This is what I needed, and I put it in my
menu.

SteveT

Steve Litt

http://444domains.com

--
--
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/20250209223130.4ef3ef94%40mydesk.domain.cxm.

Re: Is there a command line way to run gvim with a #ccffff color background?

On Sun, Feb 9, 2025 at 9:39 PM <chainsaw@fourbarlinkage.net> wrote:
>
> On Sunday, Feb 09, 2025 at 03:28 PM
> Steve Litt <slitt@troubleshooters.com> wrote:
>
> > Is there a command line way to run gvim with a #ccffff color
> > background?
> >
> > Thanks
> >
> > SteveT
> >
> > Steve Litt
> > http://444domains.com
> >
>
>
> :highlight Normal guibg=#ccffff

To run it always with that background, add the above line to your vimrc.

To do it once, run either
gvim --cmd "hi Normal guibg=#ccffff"
or
gvim -c "hi Normal guibg=#ccffff"

see
:help hl-Normal
:help highlight-guibg
:help --cmd
:help -c

Best regards,
Tony.

--
--
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/CAJkCKXt%2BCVyKiO3-CRY6qurr0xRXmpZ4sgkGnGZSRnUH7yPKbQ%40mail.gmail.com.

Re: Is there a command line way to run gvim with a #ccffff color background?

On Sunday, Feb 09, 2025 at 03:28 PM
Steve Litt <slitt@troubleshooters.com> wrote:

> Is there a command line way to run gvim with a #ccffff color
> background?
>
> Thanks
>
> SteveT
>
> Steve Litt
> http://444domains.com
>

:highlight Normal guibg=#ccffff

--
--
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/20250209153924.00001daa%40fourbarlinkage.net.

Is there a command line way to run gvim with a #ccffff color background?

Is there a command line way to run gvim with a #ccffff color background?

Thanks

SteveT

Steve Litt
http://444domains.com

--
--
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/20250209152842.3c2f98f5%40mydesk.domain.cxm.

Monday, February 3, 2025

Re: Problem with keyboard mapping

If you're on a Mac, the keyboard shortcuts may override the vim mappings you have. In this case, it turns out that this post helped : https://apple.stackexchange.com/a/423974

There was a keyboard shortcut for switching input sources and once that was disabled, then the vim mapping worked as expected.

Thanks,

Ven

On Fri, Jan 3, 2025 at 8:54 AM Ven Tadipatri <vtadipatri@gmail.com> wrote:

Yes, the nnoremap worked perfectly! It looks to be an issue with Ctrl+space for some reason.
Thank you so much Igbanam for your help - I was struggling with this for several months and was ready to give up on getting the vim mapping right.

Thanks,
Ven

On Thu, Jan 2, 2025 at 4:24 PM Igbanam Ogbuluijah <xigbanam@gmail.com> wrote:
Could you try this mapping

nnoremap <leader><space> :SWSqlExecuteCurrent<CR>

I don't know how the leader key would work with <C-space> (which I read as <ctrl><space>).

Igbanam

On Thu, Jan 2, 2025 at 5:47 PM Ven Tadipatri <vtadipatri@gmail.com> wrote:
Hi,
I have the Vim Sql Workbench plugin, and I'm trying to get the keyboard shortcut working. When I type ":nmap", I see that this mapping is there:
n \<C-Space> @:SWSqlExecuteCurrent<CR>

However, when I type "backslash - ctrl - space" , the Terminal just flashes and does nothing. I've tried using a different leader key, and the same thing happens, so it doesn't seem to be a Mac Terminal setting.
This is on a mac, with vim 9.1 . On my old mac, this keymapping was working. It still works if I type ":SWSqlExecuteCurrent", it's just the keyboard shortcut that I'm struggling with.
Would appreciate any help!

Thanks,
Ven

--
--
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/CAEodY67Vww8pR%2B6K24T33YcKgsBXw97byZPYWa9YXrb4Z-3jVg%40mail.gmail.com.

--
--
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/CAOmRJrcZZB_kgtTSDz%3DAXUsmTp%3D0paqMv4hi%3D_6CK%3DtYaei2Mw%40mail.gmail.com.