This is intended to be a vim turd file reference (please improve!)

Please add information so that this serves as a vim turd file reference.

Moving my vim setup over from Windows XP to Windows 10, I ran a few
experiments today trying to figure out how best to set up vim on Windows 10
so that the turd files it leaves (a) don't jump around, and (b) don't
clutter up the current directory.

0. https://s12.postimg.org/nezeiaxi5/00_gvim_setup.jpg
1. https://s13.postimg.org/heacohyfr/01_gvim_setup.jpg
2. https://s1.postimg.org/etb4r7nbj/02_gvim_setup.jpg
3. https://s24.postimg.org/4ubjqqo91/03_gvim_setup.jpg
4. https://s2.postimg.org/mxku3cuy1/04_gvim_setup.jpg
5. https://s18.postimg.org/6a1wh5t55/05_gvim_setup.jpg
6. https://s18.postimg.org/j11l1p4x5/06_gvim_setup.jpg
7. https://s29.postimg.org/auknub1uf/07_gvim_setup.jpg

0. Here are my _vimrc turd-file settings (also included below).
C:\apps\editor\txt\gvim\_vimrc
set directory=C:\\tmp\vim\directory//,%TMP%,C:\WINDOWS\Temp//,$HOME,.
set backupdir=C:\\tmp\vim\backupdir//,%TMP%,C:\WINDOWS\Temp//,$HOME,.
set undodir=C:\\tmp\vim\undodir//,%TMP%,C:\WINDOWS\Temp//,$HOME,.
https://s12.postimg.org/nezeiaxi5/00_gvim_setup.jpg

1. The file simply exists (there are no turd files)
FILE = C:\data\test\foo.txt
swap turd = C:\tmp\vim\directory\{empty}
backup turd = C:\tmp\vim\backupdir\{empty}
undo turd = C:\tmp\vim\undodir\{empty}
https://s13.postimg.org/heacohyfr/01_gvim_setup.jpg

2. The file is opened for edit
A swap file is created in "directory", named C:%%data%test%foo.txt.swp
FILE = C:\data\test\foo.txt
swap turd = C:\tmp\vim\directory\C:%%data%test%foo.txt.swp
backup turd = C:\tmp\vim\backupdir\{empty}
undo turd = C:\tmp\vim\undodir\{empty}
https://s1.postimg.org/etb4r7nbj/02_gvim_setup.jpg

3. The swap file is a lock turd that contains crash-recovery information:
https://s24.postimg.org/4ubjqqo91/03_gvim_setup.jpg

4. The file is saved
A backup file is created in "backupdir", named foo.txt~
FILE = C:\data\test\foo.txt
swap turd = C:\tmp\vim\directory\C:%%data%test%foo.txt.swp
backup turd = C:\tmp\vim\backupdir\foo.txt~
undo turd = C:\tmp\vim\undodir\{empty}
https://s2.postimg.org/mxku3cuy1/04_gvim_setup.jpg

5. This backup is just a copy of the original file before any edits
https://s18.postimg.org/6a1wh5t55/05_gvim_setup.jpg

6. An edit is introduced
This creates an undo file in "undodir", named C%%data%test%foo.txt
FILE = C:\data\test\foo.txt
swap turd = C:\tmp\vim\directory\C:%%data%test%foo.txt.swp
backup turd = C:\tmp\vim\backupdir\foo.txt~
undo turd = C:\tmp\vim\undodir\C%%data%test%foo.txt
https://s18.postimg.org/j11l1p4x5/06_gvim_setup.jpg

7. The undo file contains undo changes
https://s29.postimg.org/auknub1uf/07_gvim_setup.jpg

Please improve so that this thread serves as a vim turd file reference.
(Note: Linux added as their users know vim rather well so they can help!)
" " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " "
" My user edits are below this line (where doublequote starts a comment)
" The default vimrc is located at: " C:\Program Files (x86)\Vim\_vimrc
" Typing the ":version" command lists rc file locations.
" Vim settings are in _givmrc (which is always sourced)
" GVim settings are in _gvmrc (which is also sourced if the GUI is invoked)
" Using separate _vimrc & _gvimrc files avoids if-then-else clutter:
" if has("win32") || has("win64")
" set directory=$TEMP,. " swap filescurrent dir
" set backupdir=C:\temp,$HOME,. " backup files
" set undodir=C:\temp,$HOME,. " undo files
" endif
" if has("gui_win32") || has("gui_win64")
" syntax on
" colo desert
" set guifont=Consolas:h12
" endif
" " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " "
" Given a file being edited that is named foo.txt, the defaults a
" .foo.txt.swap is a temporary swap file while editing (& lock/undo file)
" .foo.txt~ is a temporary backup of the original file before editing
" .foo.txt.un~ is a temporary undo file after editing
" " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " "
" Default Windows temporary directories a
" Start Run %TMP% is C:\Users\usr1\AppData\Local\Temp
" Start Run %TEMP% is C:\Users\usr1\AppData\Local\Temp
" " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " "
" Double trailing slashes make the otherwise centralized swap files use
" filenames that are based on the full pathname of the edited file
" (this prevents swap file name collisions when editing two files of the
" same name at the same time, e.g., README files)
" EXAMPLE: set directory=c:\\tmp//,c:\\temp//
" Comma-separated values sequence in case directories don't exist
" A dot (.) means the current directory of the file being edited
" " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " "
" The "backupdir" is for backup files .foo.txt~
" The backup file is the last copy of the file as opened before new edits.
" Default vim behavior upon writing with "backup" turned on, is to "jump":
" a. Write the buffer to a new file name
" b. Delete the original file
" c. Rename the new file to the original file name
" With "nobackup", vim writes the buffer directly to the original file.
" set backup
" set nobackup
" set nowritebackup
set backupdir=C:\\tmp\vim\backupdir//,%TMP%,C:\WINDOWS\Temp//,$HOME,.
" " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " "
" The "directory" is for temporary swap files .foo.txt.swp
" Temporary swap files only exist during edits.
" The swap file is a lock file & a crash-recovery file.
" set swapfile
" set noswapfile
" set directory-=. (removes the directory from the sequence list)
set directory=C:\\tmp\vim\directory//,%TMP%,C:\WINDOWS\Temp//,$HOME,.
" " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " "
" The "undodir" is for undo files .foo.txt.un~
" set undofile
" set noundofile
set undodir=C:\\tmp\vim\undodir//,%TMP%,C:\WINDOWS\Temp//,$HOME,.
" " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " " "

On 06/01/17 15:58, Roy Tremblay wrote:
Please add information so that this serves as a vim turd file reference.

Moving my vim setup over from Windows XP to Windows 10, I ran a few
experiments today trying to figure out how best to set up vim on Windows 10
so that the turd files it leaves (a) don't jump around, and (b) don't
clutter up the current directory.

(Note: Linux added as their users know vim rather well so they can help!)

We don't use it on microsoft infected machines, so there is no help we
can offer you, so please keep us out of you migration

Roy Tremblay actually wrote:

Moving my vim setup over from Windows XP to Windows 10, I ran a few
experiments today trying to figure out how best to set up vim on Windows 10
so that the turd files it leaves (a) don't jump around, and (b) don't
clutter up the current directory.

BTW, here is an example of the turd files jumping about by default:
https://s9.postimg.org/70klfzqgf/gvim_turd_files.gif

"J.O. Aho" actually wrote:

We don't use it on microsoft infected machines, so there is no help we
can offer you, so please keep us out of you migration

Are you sure vim isn't the "vi" that is included with most linux systems?
And that the dotfile setup is almost exactly the same?

Putting it bluntly, my research implies your statement is factually wrong.
Or am I wrong?

This says the vi on "most UNIX systems" is vim!
http://www.vim.org/

This says the default vi on Ubuntu is vim!
https://askubuntu.com/questions/1110...default#111022

Even if it's not the default Ubuntu editor, it's on Ubuntu for su
https://www.cyberciti.biz/faq/howto-...-ubuntu-linux/

This article says it's the top text editor on Linux:
Top 5 Best Linux Text Editors
http://www.thegeekstuff.com/2009/07/...x-text-editors

This article says vim is just a newer version of vi on Linux:
http://www.hostingadvice.com/blog/5-...editors-linux/

Linux.org also equates vim as a newer version of vi on Linux:
https://www.linux.org/threads/text-editors.4134/

This shows that VIM is on Redhat/Centos/Fedora & Debian/Ubuntu:
http://www.yolinux.com/TUTORIALS/Lin...vanced_vi.html

How can you claim, in the wake of that evidence, that most Linux "vi"
installations aren't just "vim" with an alias to vi?

On 01/06/2017 21:14, Roy Tremblay wrote:
Roy Tremblay actually wrote:

Moving my vim setup over from Windows XP to Windows 10, I ran a few
experiments today trying to figure out how best to set up vim on Windows 10
so that the turd files it leaves (a) don't jump around, and (b) don't
clutter up the current directory.
BTW, here is an example of the turd files jumping about by default:
https://s9.postimg.org/70klfzqgf/gvim_turd_files.gif

For ( a ) I assume you are talking about Desktop Icons. If this is so
then Right-Click on your Desktop and then change the settings as shown
in this pictu


https://i.cubeupload.com/DuT1Xn.png https://i.cubeupload.com/DuT1Xn.png



--
With over 500 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

On 2017-06-01, Roy Tremblay wrote:
"J.O. Aho" actually wrote:

We don't use it on microsoft infected machines, so there is no help we
can offer you, so please keep us out of you migration

Are you sure vim isn't the "vi" that is included with most linux systems?
And that the dotfile setup is almost exactly the same?

Putting it bluntly, my research implies your statement is factually wrong.
Or am I wrong?

This says the vi on "most UNIX systems" is vim!
http://www.vim.org/

This says the default vi on Ubuntu is vim!
https://askubuntu.com/questions/1110...default#111022

Even if it's not the default Ubuntu editor, it's on Ubuntu for su
https://www.cyberciti.biz/faq/howto-...-ubuntu-linux/

This article says it's the top text editor on Linux:
Top 5 Best Linux Text Editors
http://www.thegeekstuff.com/2009/07/...x-text-editors

This article says vim is just a newer version of vi on Linux:
http://www.hostingadvice.com/blog/5-...editors-linux/

Linux.org also equates vim as a newer version of vi on Linux:
https://www.linux.org/threads/text-editors.4134/

This shows that VIM is on Redhat/Centos/Fedora & Debian/Ubuntu:
http://www.yolinux.com/TUTORIALS/Lin...vanced_vi.html

How can you claim, in the wake of that evidence, that most Linux "vi"
installations aren't just "vim" with an alias to vi?

We can absolutely tell you whether vi is an alias to vim or not.

#!/bin/bash

################################################## ######################
#
# script: packinfo
# version: .01
# date: 2017-06-01
# by: Marek Novotny
# purpose: get package info
# : for debian, redhat and arch linux
#
################################################## ######################

app_name=$(basename $0)
prg_name=$1

if [ $# -ne 1 ]
then
echo "usage: $app_name {program name}"
exit 1
fi

report ()
{
printf "%${mtab}s %s \n" "Program name:" "$prg_name"
printf "%${mtab}s %s \n" "Location:" "$prg_path"
printf "%${mtab}s %s \n\n" "Package:" "${package:=none}"

for x in ${packinfo[@]} ; do
printf "$x \n"
done
}

get_package_info ()
{
# debian systems
dpkg -S $prg_path & /dev/null
if [ $? -eq 0 ] ; then
package="$(dpkg -S $prg_path | cut -d':' -f1)"

IFS=$'\n'
packinfo=($(dpkg -p $package))
let mtab=13
report
fi

# redhat systems
rpm -qf $prg_path & /dev/null
if [ $? -eq 0 ] ; then
package="$(rpm -qf $prg_path)"

IFS=$'\n'
packinfo=($(rpm -qi $package))
let mtab=13
report
fi

# arch systems
pacman -Qo $prg_path & /dev/null
if [ $? -eq 0 ] ; then
set -- $(pacman -Qo $prg_path)
while [ $1 != "by" ] ; do
shift
package="$2"
done

IFS=$'\n'
packinfo=($(pacman -Qi $package))
let mtab=17
report
fi
}

prg_path=$(which $prg_name 2 /dev/null)
if [ $? -eq 0 ] ; then
get_package_info
else
echo "not found..."
fi

## end ##

Now you can check for yourself if you're so inclined. We'd all
appreciate it if you'd keep your Windows bull**** off the linux group.
If you have a *linux* question feel free to ask in the *linux* group.
Otherwise, we're not interested.

--
Marek Novotny
https://github.com/marek-novotny

Marek Novotny actually wrote:

Now you can check for yourself if you're so inclined. We'd all
appreciate it if you'd keep your Windows bull**** off the linux group.
If you have a *linux* question feel free to ask in the *linux* group.
Otherwise, we're not interested.

I researched and lurked BEFORE I had asked the question and written the
tutorial to help others, like you often do.

So, respectfully, I have to say that the evidence shows that VIM is on
Linux in a very common way.

BTW, I respect you Marek, from lurking on a.o.l where I know your opinion
and code-writing help is always respected (I hope the warfarin is working
well as you had everyone scared for a few weeks a while ago when you
disappeared for a few months).

Respectfully, I note that you addressed "a" question, but not the key
question.

However, you didn't address the key question, which I very respectfully
repeat which is whether vim is on Linux, where you and J.O. Aho imply it's
not, but that's like denying that the sky is blue.

It seems overwhelimingly so that Vim is on Linux and, in fact, it's the
default vi editor on some Linux variants.

Is that not a true statement overall?

NOTE: I will set the followup to exclude a.o.l and I will NOT reply to
a.o.l again on this subject, so if you want to answer the basic question,
then it will have to be on the windows ng as you suggested we do.

Good Guy actually wrote:

Moving my vim setup over from Windows XP to Windows 10, I ran a few
experiments today trying to figure out how best to set up vim on Windows 10
so that the turd files it leaves (a) don't jump around, and (b) don't
clutter up the current directory.
BTW, here is an example of the turd files jumping about by default:
https://s9.postimg.org/70klfzqgf/gvim_turd_files.gif

For ( a ) I assume you are talking about Desktop Icons. If this is so
then Right-Click on your Desktop and then change the settings as shown
in this pictu


https://i.cubeupload.com/DuT1Xn.png https://i.cubeupload.com/DuT1Xn.png

Thanks for that grid suggestion but that's not what the "jumping around"
means.

The "jumping around" is a term others use, which I found when I was trying
to "get rid of" the turd files.

They call it "jumping files" on stackexchange:
https://stackoverflow.com/questions/...th-a-extension

The "jumping files" refers to the fact that vim actually moves files around
when you save, by default, hence they flash in your face as they disappear
and reappear as a different incarnation every time you save

I'm not sure exactly the sequence but it goes something like this:
a. You open foo.txt
b. That creates the swap file which you can see
c. You edit foo.txt & save
d. That actually saves the buffer to something else
e. Then that deletes the foo.txt file so it disappears momentarily
f. Then it copies the saved file over to foo.txt so it reappears
g. Then it deletes the file it saved from the buffer
h. Meanwhile, there can be backup and undo files showing up

The whole thing entails a bunch of files "jumping around" on your screen
(not only on the desktop, but anywhere you can see the file system while
you're saving).


NOTE: Removed a.o.l because they "claim" vim isn't the most common text
editor on Linux variants; but the evidence appears to show otherwise.
(I think they just don't realize it because of the aliases they use.)

On 2017-06-01, Roy Tremblay wrote:
Marek Novotny actually wrote:

Now you can check for yourself if you're so inclined. We'd all
appreciate it if you'd keep your Windows bull**** off the linux group.
If you have a *linux* question feel free to ask in the *linux* group.
Otherwise, we're not interested.

I researched and lurked BEFORE I had asked the question and written the
tutorial to help others, like you often do.

No research is needed. You can simply ask the package manager what
provides the command. That's what the script does that I wrote for you.
To use it, you type, the script itself with one single argument, which
would be a command and it will tell you what it comes from.

{script name} vi

And out will come what package and the details of the package that
provided that command. If the package is vim then it is vim. It should
work on any debian, redhat or arch based linux distribution such as
debian, mint, ubuntu, redhat, centos, fedora, arch, manjaro and so on.

So, respectfully, I have to say that the evidence shows that VIM is on
Linux in a very common way.

It is. But again, you don't have to look at what other sites say and
present evidence based on what a lot of misc sites say. Instead, you can
*know* the answer first-hand by asking the distro itself where the
command comes from. What package provided that command.

Make sense?

BTW, I respect you Marek, from lurking on a.o.l where I know your opinion
and code-writing help is always respected (I hope the warfarin is working
well as you had everyone scared for a few weeks a while ago when you
disappeared for a few months).

Respectfully, I note that you addressed "a" question, but not the key
question.

However, you didn't address the key question, which I very respectfully
repeat which is whether vim is on Linux, where you and J.O. Aho imply it's
not, but that's like denying that the sky is blue.

Vim is on linux. And again, anyone can *know* that by determining what
package provides the command. Sample:

Script started on Thu 01 Jun 2017 01:51:04 PM PDT
[marek@rhel7x ~]$ packinfo vi
Program name: vi
Location: /usr/bin/vi
Package: vim-minimal-7.4.160-1.el7_3.1.x86_64
Name : vim-minimal
Epoch : 2
Version : 7.4.160
Release : 1.el7_3.1
Architectu x86_64
Install Date: Sat 08 Apr 2017 05:58:04 PM PDT
Group : Applications/Editors
Size : 917704
License : Vim
Signature : RSA/SHA256, Wed 14 Dec 2016 06:32:05 AM PST, Key ID
: 199e2f91fd431d51
Source RPM : vim-7.4.160-1.el7_3.1.src.rpm
Build Date : Mon 12 Dec 2016 05:08:13 AM PST
Build Host : x86-037.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager : Red Hat, Inc. http://bugzilla.redhat.com/bugzilla
Vendor : Red Hat, Inc.
URL : http://www.vim.org/
Summary : A minimal version of the VIM editor
Description :
VIM (VIsual editor iMproved) is an updated and improved version of the
vi editor. Vi was the first real screen-based editor for UNIX, and is
still very popular. VIM improves on vi by adding new features:
multiple windows, multi-level undo, block highlighting and more. The
vim-minimal package includes a minimal version of VIM, which is
installed into /bin/vi for use when only the root partition is
present. NOTE: The online help is only available when the vim-common
package is installed.
[marek@rhel7x ~]$ exit
exit

Script done on Thu 01 Jun 2017 01:51:12 PM PDT

It seems overwhelimingly so that Vim is on Linux and, in fact, it's the
default vi editor on some Linux variants.

You can ask the distro itself what provides the command.

Is that not a true statement overall?

I can't imagine any modern Linux not using Vim. Typically, if you just
type vi or vim and open an empty buffer, it will announce what it is.

NOTE: I will set the followup to exclude a.o.l and I will NOT reply to
a.o.l again on this subject, so if you want to answer the basic question,
then it will have to be on the windows ng as you suggested we do.

In general, if it is a Windows issue, just ask in the windows group.
We're getting a lot of cross-posting for trolling purposes and you're
just going to end up in everyone's killfile pretty fast because we're
all sick of it at this point and just sticking everything with a cross
post in the kill file. If you have a real and serious question, just ask
without the cross-post. I did note why the post was cross-posted. I'm a
long time Vim user myself, and I wouldn't be able to help a Windows user
on it because I simply have almost zero experience with Windows and Vim.
I'd imagine that's the case for most of us.

That and the post seems confrontational, which will immediately tip the
scale towards a trolling post and again, you'll wind up in everyone's
kill file.

So, you have a script now. The script will work on a lot of distros and
will tell you what package the command comes from and give you details
about the package itself. If someone says their distro is using vi, they
can use that script to see if that's true.

They can also use the script command called, *script* to share the
output. Syntax is script out.txt

Then type whatever you want and a copy of the interactive shell session
will be sent to out.txt until you type exit. That way they can share the
interactive command and output with the group and show the results.

I hope that resolves the matter.

--
Marek Novotny
https://github.com/marek-novotny

Roy Tremblay wrote:

Marek Novotny actually wrote:

Now you can check for yourself if you're so inclined. We'd all
appreciate it if you'd keep your Windows bull**** off the linux group.
If you have a *linux* question feel free to ask in the *linux* group.
Otherwise, we're not interested.

I researched and lurked BEFORE I had asked the question and written the
tutorial to help others, like you often do.

So, respectfully, I have to say that the evidence shows that VIM is on
Linux in a very common way.

Yes, and linux users don't need the "help" of a blubbering fool and wintendo
luser with info which is windows-specific

You "lurked" about the "success" (or lack thereof) of that brainless cretin
"Good Guy" who purposefully posts windows-stuff to linux groups to annoy
people who without any exception are far more smarter than that idiot

Roy Tremblay wrote:
Roy Tremblay actually wrote:

Moving my vim setup over from Windows XP to Windows 10, I ran a few
experiments today trying to figure out how best to set up vim on Windows 10
so that the turd files it leaves (a) don't jump around, and (b) don't
clutter up the current directory.

BTW, here is an example of the turd files jumping about by default:
https://s9.postimg.org/70klfzqgf/gvim_turd_files.gif

Linux is available as a subsystem in Windows 10.

It's called the Bash shell, because it lacks Xorg on purpose.

You should be able to run vim from there if you want.

People have even run some version of Xorg from Windows 10
anyway (to give it a display subsystem), then installed
Linux Firefox and run Firefox from the Linux subsystem.

Since VIM looks like an ncurses program, you should
have no trouble running it in the Bash shell.

All your Windows drive letters are mounted in Bash,
so perhaps /mnt/C/foldername in Bash shell, is the same thing
as C:\foldername in Command Prompt. That was one detail that
wasn't apparent the first time I used it.

https://www.howtogeek.com/249966/how...on-windows-10/

If VIM isn't in the Bash shell in Windows 10, you
could do the usual sort of stuff. The Bash shell has
some sort of package manager, and the Ubuntu repository
is represented.

apt install vim

While you can "see" /mnt/C , you cannot use physical level
utilities. dd if=/dev/sda would not work, if C: was in
sda. That level of physicality is missing. Just the
virtual mounts are visible.

HTH,
Paul

Marek Novotny actually wrote:

Vim is on linux. And again, anyone can *know* that by determining what
package provides the command. Sample:

Hi Marek,
I respect you for all the help you provide others in coding, so it is to
you that I say that we are both saying the same thing which is that vim is
on linux.

Since (a) VIM is on Linux, and since (b) the ~/.vimrc file is the same
syntax on linux as on Windows, and since (c) Linux users know vimrc files
well, I had correctly assumed that putting Linux on the ng line is apropos.

What I did not realize was the utter inconsolable hatred that there is for
this troll named "Good Guy" and the unrealistic hatred of anything related
to both Windows and Linux (such as that which J.O. Aho displayed) was so
severe.

Hence, what I didn't realize was that discussing vimrc files with the Linux
users was just going to waste everyone's time, including yours and mine
when we could better spend our time helping people in our own ways.

So I'm sorry I asked anything about vimrc files of the Linux users.
But, you've helped me greatly in the past and I do appreciate you.

Peter Köhlmann actually wrote:

Yes, and linux users don't need the "help" of a blubbering fool and wintendo
luser with info which is windows-specific

Your utter hatred shows in that you don't realize that the vimrc file
settings are the same in both Windows and in Linux.

Since there is so much hatred going on here, I am sorry that I brought
Linux users into the ~/.vimrc discussion since their hatred prevents them
from (a) benefiting from the information, and worse (b) they just cloud the
thread with their incorrect protests that vim isn't on Linux (which is like
saying the sky isn't blue).

I'm sorry I even tried to help the linux users at all. I really am.
I respect them. But their hatred is too overwhelming for them to benefit.

On 2017-06-02, Roy Tremblay wrote:
Marek Novotny actually wrote:

Vim is on linux. And again, anyone can *know* that by determining what
package provides the command. Sample:

Hi Marek,
I respect you for all the help you provide others in coding, so it is to
you that I say that we are both saying the same thing which is that vim is
on linux.

Since (a) VIM is on Linux, and since (b) the ~/.vimrc file is the same
syntax on linux as on Windows, and since (c) Linux users know vimrc files
well, I had correctly assumed that putting Linux on the ng line is apropos.

What I did not realize was the utter inconsolable hatred that there is for
this troll named "Good Guy" and the unrealistic hatred of anything related
to both Windows and Linux (such as that which J.O. Aho displayed) was so
severe.

Hence, what I didn't realize was that discussing vimrc files with the Linux
users was just going to waste everyone's time, including yours and mine
when we could better spend our time helping people in our own ways.

So I'm sorry I asked anything about vimrc files of the Linux users.
But, you've helped me greatly in the past and I do appreciate you.

Lot's of us love vim and would love to discuss vimrc files all day long.
We just don't want the cross-posting between windows and linux which
ends up being nothing more than every post in the windows group being
echo'd into our group. We're not participating which ought to be a cue
to stop what you're doing.

--
Marek Novotny
https://github.com/marek-novotny

On 2017-06-02, Roy Tremblay wrote:
Peter Köhlmann actually wrote:

Yes, and linux users don't need the "help" of a blubbering fool and wintendo
luser with info which is windows-specific

Your utter hatred shows in that you don't realize that the vimrc file
settings are the same in both Windows and in Linux.

This confrontation is not good for either group.

Since there is so much hatred going on here, I am sorry that I brought
Linux users into the ~/.vimrc discussion since their hatred prevents them
from (a) benefiting from the information, and worse (b) they just cloud the
thread with their incorrect protests that vim isn't on Linux (which is like
saying the sky isn't blue).

I'm sorry I even tried to help the linux users at all. I really am.
I respect them. But their hatred is too overwhelming for them to benefit.

Honestly, we're not in need of it. We're typically the ones providing
the help, not asking for it. We're there to help those in genuine need
of it. It's not a chit-chat group either. That's what advocacy groups
are for. The only thing that should be in that group is a serious
question from someone who actually needs help on linux. Everything else
we call noise. And we like to keep the signal to noise ratio in check if
possible.

Thanks in advance.

--
Marek Novotny
https://github.com/marek-novotny