mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
parent
89781f578e
commit
b475f28979
|
@ -1973,7 +1973,7 @@ Vim-HOWTO</ULink>,
|
||||||
<CiteTitle>Vim Color Editor HOWTO (Vi Improved w/syntax
|
<CiteTitle>Vim Color Editor HOWTO (Vi Improved w/syntax
|
||||||
color highlighting)</CiteTitle>
|
color highlighting)</CiteTitle>
|
||||||
</Para><Para>
|
</Para><Para>
|
||||||
<CiteTitle>Updated: July 2000</CiteTitle>.
|
<CiteTitle>Updated: August 2000</CiteTitle>.
|
||||||
A guide to very quickly setup Vim color editor on Linux or Unix systems. </Para>
|
A guide to very quickly setup Vim color editor on Linux or Unix systems. </Para>
|
||||||
</ListItem>
|
</ListItem>
|
||||||
|
|
||||||
|
|
|
@ -394,8 +394,9 @@ Vim-HOWTO</ULink>,
|
||||||
<CiteTitle>Vim Color Editor HOWTO (Vi Improved w/syntax
|
<CiteTitle>Vim Color Editor HOWTO (Vi Improved w/syntax
|
||||||
color highlighting)</CiteTitle>
|
color highlighting)</CiteTitle>
|
||||||
</Para><Para>
|
</Para><Para>
|
||||||
<CiteTitle>Updated: July 2000</CiteTitle>.
|
<CiteTitle>Updated: August 2000</CiteTitle>.
|
||||||
A guide to very quickly setup Vim color editor on Linux or Unix systems. </Para>
|
A guide to very quickly setup Vim color editor on Linux or Unix
|
||||||
|
systems. </Para>
|
||||||
</ListItem>
|
</ListItem>
|
||||||
|
|
||||||
<ListItem>
|
<ListItem>
|
||||||
|
|
|
@ -5,7 +5,7 @@
|
||||||
|
|
||||||
<title>Linux+WindowsNT mini-HOWTO
|
<title>Linux+WindowsNT mini-HOWTO
|
||||||
<author>Miroslav Skoric, <tt/m.skoric@eunet.yu/
|
<author>Miroslav Skoric, <tt/m.skoric@eunet.yu/
|
||||||
<date>v2.1, 01 August 2000
|
<date>v2.2, 07 August 2000
|
||||||
<abstract>
|
<abstract>
|
||||||
<nidx>windows nt</nidx>
|
<nidx>windows nt</nidx>
|
||||||
This mini-HOWTO covers some ways on how to install both Linux and Windows
|
This mini-HOWTO covers some ways on how to install both Linux and Windows
|
||||||
|
@ -50,12 +50,10 @@ in order to get some free space for your further Linux' partitions.
|
||||||
Of course you all are able to install Windows NT first and after that
|
Of course you all are able to install Windows NT first and after that
|
||||||
Linux. We'll see how to do that and how to use <bf/LILO/ (<bf/Li/nux
|
Linux. We'll see how to do that and how to use <bf/LILO/ (<bf/Li/nux
|
||||||
<bf/Lo/ader) to choose which operating system to boot. But, before that
|
<bf/Lo/ader) to choose which operating system to boot. But, before that
|
||||||
we'll see the procedure that the previous maintainer of this mini-HOWTO
|
we'll see the procedure that Bill Wohler, the previous maintainer of
|
||||||
has been using:
|
this mini-HOWTO, has been using:
|
||||||
|
|
||||||
<sect>INSTALLATION
|
<sect>HOW TO INSTALL: LINUX FIRST, WINDOWS NT AFTER
|
||||||
|
|
||||||
<sect1>Linux first, NT after
|
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
1. Install a minimal Linux (hold off on installing the rest until
|
1. Install a minimal Linux (hold off on installing the rest until
|
||||||
|
@ -179,10 +177,11 @@ Partition 1 does not end on cylinder boundary:
|
||||||
subject. I should point you to an appropriate Linux newsgroup for
|
subject. I should point you to an appropriate Linux newsgroup for
|
||||||
further information. I use NT about one day a year. Under duress.
|
further information. I use NT about one day a year. Under duress.
|
||||||
|
|
||||||
<sect1>NT first, Linux after
|
|
||||||
|
<sect>HOW TO INSTALL: WINDOWS NT FIRST, LINUX AFTER
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<sect2>2.2.1 If you have <em>only one</em> IDE hard disk
|
<sect1>If you have <em>only one</em> IDE hard disk
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<itemize>
|
<itemize>
|
||||||
|
@ -259,16 +258,58 @@ Partition 1 does not end on cylinder boundary:
|
||||||
Windows NT has been installed, so you could add an appropriate
|
Windows NT has been installed, so you could add an appropriate
|
||||||
entry into /etc/lilo.conf file. After you do that, restart Lilo
|
entry into /etc/lilo.conf file. After you do that, restart Lilo
|
||||||
and, after the next re-boot, you will have both 'linux' and 'nt'
|
and, after the next re-boot, you will have both 'linux' and 'nt'
|
||||||
entries under Lilo menu. My added NT entry is:
|
entries under Lilo menu.
|
||||||
|
|
||||||
|
<p>
|
||||||
|
<item>My added NT entry is:
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
other=/dev/hda1
|
other=/dev/hda1
|
||||||
|
|
||||||
label=nt
|
label=nt
|
||||||
|
|
||||||
|
<p>
|
||||||
|
So, the whole /etc/lilo.conf looks like this:
|
||||||
|
|
||||||
|
<p>
|
||||||
|
boot=/dev/hda
|
||||||
|
|
||||||
|
timeout=50
|
||||||
|
|
||||||
|
prompt
|
||||||
|
|
||||||
|
default=linux
|
||||||
|
|
||||||
|
vga=normal
|
||||||
|
|
||||||
|
read-only
|
||||||
|
|
||||||
|
image=/boot/vmlinuz-2.2.12-20
|
||||||
|
|
||||||
|
label=linux
|
||||||
|
|
||||||
|
root=/dev/hda3
|
||||||
|
|
||||||
|
other=/dev/hda1
|
||||||
|
|
||||||
|
label=nt
|
||||||
|
|
||||||
|
<p>
|
||||||
|
<item>Some more explanations regarding details from my /etc/lilo.conf
|
||||||
|
file: After I have installed Windows NT, I assigned the letter C:
|
||||||
|
to that drive. Beside that, I wanted to have another NTFS
|
||||||
|
partition in order to store and backup important files, case I
|
||||||
|
have to re-install NT on C: for some reason in the future. That's why
|
||||||
|
I've made another NT partition, that has been assigned as D: disk.
|
||||||
|
Both NTFS partitions are approximatelly 3 GB each and Linux setup
|
||||||
|
found them as /dev/hda1 and /dev/hda2 partitions. The rest free space
|
||||||
|
on the disk was cca 2 GB, where I have made the /root partition of
|
||||||
|
near 1.9 GB and /swapp part of cca 100 MB (/dev/hda3 and /dev/hda4
|
||||||
|
respectively). Lilo went to the MBR and all has been running fine.
|
||||||
|
|
||||||
</itemize>
|
</itemize>
|
||||||
|
|
||||||
<sect2>2.2.2 If you have <em>more than one</em> (SCSI) hard disk
|
<sect1>If you have <em>more than one</em> (SCSI) hard disk
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<em>Notice: Folks, you see, at my place, one of computers has several
|
<em>Notice: Folks, you see, at my place, one of computers has several
|
||||||
|
@ -276,7 +317,7 @@ SCSI disks. That's why I put the word 'SCSI' in parentheses. There I
|
||||||
have several SCSI controllers, SCSI CD ROM drive and SCSI Tape drive.
|
have several SCSI controllers, SCSI CD ROM drive and SCSI Tape drive.
|
||||||
So, it doesn't mean that *you* will be using SCSI parts at all.
|
So, it doesn't mean that *you* will be using SCSI parts at all.
|
||||||
You'd rather handle more than one IDE disks, but I hope that install
|
You'd rather handle more than one IDE disks, but I hope that install
|
||||||
process shouldn't change too much, if any.
|
process shouldn't change too much, if any.
|
||||||
</em>
|
</em>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
@ -307,13 +348,13 @@ process shouldn't change too much, if any.
|
||||||
So, it is advisible to 'shrink' the partition where NT resides
|
So, it is advisible to 'shrink' the partition where NT resides
|
||||||
in order to make some free space on the disk. Onto that free space
|
in order to make some free space on the disk. Onto that free space
|
||||||
you will install your Linux. Well, you may also think of using
|
you will install your Linux. Well, you may also think of using
|
||||||
some other disk(s) you have for Linux (so did I). That case, you
|
other disk(s) you have for Linux (so did I). That case, you
|
||||||
would start your linux installation and try to use, for example,
|
would start your linux installation and tried to use, for example,
|
||||||
/dev/sdb (or sdc, or sdd, or else in case of SCSI system) or
|
/dev/sdb (or sdc, or sdd, or else in case of SCSI system) or
|
||||||
/dev/hdb (or hdc, or hdd, or else in case of IDE system). Looks
|
/dev/hdb (or hdc, or hdd, or else in case of IDE system). Looked
|
||||||
like Linux installation accepts whatever you choose, but somehow
|
that Linux installation accepted whatever I chose, but somehow
|
||||||
after all was finished when I did that, LILO was no able to
|
after all was finished, when I did that, LILO was not able to
|
||||||
do anything. Actually, it always stopped after 'LI' so it was
|
do anything. Actually, it always stopped after 'LI' so it was not
|
||||||
possible to start Linux at all. Finally, after pulling my hair
|
possible to start Linux at all. Finally, after pulling my hair
|
||||||
out, I decided to make it all on the <bf/first/ disk. So, after
|
out, I decided to make it all on the <bf/first/ disk. So, after
|
||||||
I had NT configured and running, I had to boot my computer using
|
I had NT configured and running, I had to boot my computer using
|
||||||
|
@ -322,22 +363,24 @@ process shouldn't change too much, if any.
|
||||||
have. The best thing is that you can make some changes with your
|
have. The best thing is that you can make some changes with your
|
||||||
partitions but not to destroy your existing data. One of the
|
partitions but not to destroy your existing data. One of the
|
||||||
available changes is to make your existing partition(s) smaller,
|
available changes is to make your existing partition(s) smaller,
|
||||||
so to get some free space on the disk(s) for other purposes.
|
so you can get some free space on the disk(s) for other purposes.
|
||||||
Although you are advised to make a backup before you make any
|
Although you are advised to make a backup before you make any
|
||||||
changes to the partitions, I usually practise to 'shrink' NT's
|
changes with your partitions, I usually practise to 'shrink' NT's
|
||||||
partition before I installed anything but NT itself (so, if
|
partition <em>before</em> I install anything but NT itself (so, if
|
||||||
needed, a repetitive re-installation wouldn't be a problem).
|
needed, a repetitive re-installation wouldn't be a problem).
|
||||||
Well, Partition Magic (or any other similar utility you are
|
Well, Partition Magic (or any other similar utility you are
|
||||||
familiar with) will shrink your NT's partition (either NTFS or
|
familiar with) will shrink your NT's partition (either NTFS or
|
||||||
FAT) to a smaller measure and place it to either the beginning
|
FAT) to a smaller measure and place it to either the beginning
|
||||||
or to the end of the previous measure. It means that you may
|
or to the end of the previous measure. It means that you may
|
||||||
choose to have your 'shrinked' NT partition at the beginning
|
choose to have your 'shrinked' NT partition at the beginning
|
||||||
or at the end of your disk (I usually choose NT to be at the
|
or at the end of your disk. I usually choose NT to be at the
|
||||||
beginning, so the ending part of the disk will become a 'free
|
beginning, so the ending part of the disk will become a 'free
|
||||||
space'). After the 'shrinkin' is finished, you may re-boot your
|
space'. I discovered some problems if the 'free space' is made
|
||||||
|
at the beginning of disk (later we'll talk about). So, after the
|
||||||
|
'shrinkin' is finished, you may re-boot your
|
||||||
NT in order to check the new situation: you may use Windows
|
NT in order to check the new situation: you may use Windows
|
||||||
Explorer or Disk Administrator for that. You will note that
|
Explorer or Disk Administrator for that. You will also note how
|
||||||
NT 'sees' all other disks you have in your machine (either
|
NT can 'see' all (other) disks you have in your machine (either
|
||||||
partitioned or as 'free space' areas).
|
partitioned or as 'free space' areas).
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
|
@ -370,15 +413,124 @@ process shouldn't change too much, if any.
|
||||||
Windows NT has been installed, so you could add an appropriate
|
Windows NT has been installed, so you could add an appropriate
|
||||||
entry into /etc/lilo.conf file. After you do that, restart Lilo
|
entry into /etc/lilo.conf file. After you do that, restart Lilo
|
||||||
and, after the next re-boot, you will have both 'linux' and 'nt'
|
and, after the next re-boot, you will have both 'linux' and 'nt'
|
||||||
entries under Lilo menu. My added NT entry is:
|
entries under Lilo menu.
|
||||||
|
|
||||||
|
<p>
|
||||||
|
<item>My added NT entry is:
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
other=/dev/sda1
|
other=/dev/sda1
|
||||||
|
|
||||||
label=nt
|
label=nt
|
||||||
|
|
||||||
|
|
||||||
|
<p> so, the whole /etc/lilo.conf looks like this:
|
||||||
|
|
||||||
|
|
||||||
|
boot=/dev/sda
|
||||||
|
|
||||||
|
map=/boot/map
|
||||||
|
|
||||||
|
install=/boot/boot.b
|
||||||
|
|
||||||
|
prompt
|
||||||
|
|
||||||
|
timeout=50
|
||||||
|
|
||||||
|
default=linux
|
||||||
|
|
||||||
|
image=/boot/vmlinuz-2.2.12-20smp
|
||||||
|
|
||||||
|
label=linux-mp
|
||||||
|
|
||||||
|
initrd=/boot/initrd-2.2.12-20smp.img
|
||||||
|
|
||||||
|
read-only
|
||||||
|
|
||||||
|
root=/dev/sda6
|
||||||
|
|
||||||
|
image=/boot/vmlinuz-2.2.12-20
|
||||||
|
|
||||||
|
label=linux-up
|
||||||
|
|
||||||
|
initrd=/boot/initrd-2.2.12-20.img
|
||||||
|
|
||||||
|
read-only
|
||||||
|
|
||||||
|
root=/dev/sda6
|
||||||
|
|
||||||
|
other=/dev/hda1
|
||||||
|
|
||||||
|
label=nt
|
||||||
|
|
||||||
|
<p>
|
||||||
|
<item>Some more explanation, regarding details from my /etc/lilo.conf
|
||||||
|
file: After I have installed Windows NT on the <bf/first/ disk,
|
||||||
|
I assigned the letter C: to that drive. After I made enough free
|
||||||
|
space <em>after</em> the NTFS partition, I let Linux setup to
|
||||||
|
handle further partitioning. Although Linux should support as far
|
||||||
|
as four primary partitions per disk, it seems that Linux setup is
|
||||||
|
likely to make an extended partition, whenever it recognizes that
|
||||||
|
there is already a primary partition on the disk. Considering that
|
||||||
|
those 'virtual' primary partitions would be numbered from /dev/sda1
|
||||||
|
to /dev/sda4 (including an extended one, of course), the extended
|
||||||
|
one should become /dev/sda4. Following that idea, the first one logical
|
||||||
|
partition within the extended one was numbered as /dev/sda5 (in my
|
||||||
|
case, it was the /boot partition that physically was the first from
|
||||||
|
the beginning of the <bf/first/ hard disk). So, the /root and /swapp
|
||||||
|
partitions are /dev/sda6 and /dev/sda7 respectively. You may see a line
|
||||||
|
"root=/dev/sda6" telling you that. Once again, Lilo went to the MBR
|
||||||
|
and all has been running fine.
|
||||||
|
|
||||||
|
<p>
|
||||||
|
<item>Well, you may ask me: Ok, but what in a case I have several
|
||||||
|
hard disks installed in the machine? Good question. You see, I
|
||||||
|
myself have <em>four</em> SCSI disks and, of course, I tried to
|
||||||
|
install Linux on the 2nd one, next the 3rd and, finally, on the
|
||||||
|
4th disk. Whatever I did (Linux setup haven't complained at all),
|
||||||
|
when I was about to finish the installation and after performing the
|
||||||
|
final automatic re-boot, my Lilo would stop after 'LI' so the
|
||||||
|
computer had to be re-started. Finally, I realized that there
|
||||||
|
must be a problem with disks that are too "far" from the MBR that is
|
||||||
|
located at the beginning of the <bf/first/ hard disk. That's why
|
||||||
|
I suggest you to make them all (both NT and Linux) on your <bf/first/
|
||||||
|
disk. After having all of them running ok, there is no problem
|
||||||
|
to make other disks visible (and usable) by both operating
|
||||||
|
system. I hope your <bf/first/ disk is large enough to carry
|
||||||
|
both operating systems (NT needs at least cca 150 MB for itself,
|
||||||
|
Linux depends on what you want to get: Gnome or KDE Workstations
|
||||||
|
are about 580 MB, but the Custom wants more than 1.4 GB). That
|
||||||
|
means the <bf/first/ hard disk of cca 2.4 GB should fit.
|
||||||
|
|
||||||
|
<p>
|
||||||
|
<item>You may also ask me: Ok, but, could I 'shrink' my NT partition in
|
||||||
|
a way the 'free space' is made at the beginning of the disk? Well, I
|
||||||
|
remember I tried to do so and to install, at first, Gnome
|
||||||
|
Workstation (395 packages, 570 MB) there. During the setup, everything
|
||||||
|
looked fine, but neither Lilo was not installed, nor the boot floppy
|
||||||
|
was made. You bet, Linux was not functional. Then I tried to install
|
||||||
|
KDE Workstation (377 packages, 582 MB) on the same place. Once again,
|
||||||
|
everything looked fine, but neither Lilo was not installed, nor the
|
||||||
|
boot floppy was made. Investigating that, I studied the structure of all
|
||||||
|
existing partitions. I was surprised when recognized that new born
|
||||||
|
logical partitions (within the new extended one) were numbered as
|
||||||
|
if they were physically positioned <em>after</em> the NT partition!
|
||||||
|
In the other words, there I have a 'funny' order: /dev/sda5, /dev/sda6,
|
||||||
|
/dev/sda7 and, finally, /dev/sda1. Looked like the system was a bit
|
||||||
|
confused.
|
||||||
|
|
||||||
|
<p>
|
||||||
|
<item>Regarding two similar Linux images (differ in 'smp'). It is a server
|
||||||
|
hardware with a multi-processor support. The "inteligent" setup has
|
||||||
|
inspected the hardware and offered me to have both 'multi' and 'uni'
|
||||||
|
processor functionality. Nevertheless, I still have only one CPU
|
||||||
|
there.
|
||||||
|
|
||||||
</itemize>
|
</itemize>
|
||||||
|
|
||||||
|
<sect>FURTHER INFORMATION
|
||||||
|
|
||||||
|
<p>
|
||||||
<sect1>Copyright
|
<sect1>Copyright
|
||||||
<p>
|
<p>
|
||||||
<em>Copyright is a source of much and continuous debate on the
|
<em>Copyright is a source of much and continuous debate on the
|
||||||
|
@ -468,7 +620,7 @@ Any comments or suggestions can be mailed to my email address:
|
||||||
<htmlurl url="mailto:m.skoric@eunet.yu"
|
<htmlurl url="mailto:m.skoric@eunet.yu"
|
||||||
name="m.skoric@eunet.yu">.
|
name="m.skoric@eunet.yu">.
|
||||||
|
|
||||||
<sect>Further Information
|
|
||||||
<sect1>HOWTO
|
<sect1>HOWTO
|
||||||
<p>
|
<p>
|
||||||
<nidx>disk!information resources!HOWTOs</nidx>
|
<nidx>disk!information resources!HOWTOs</nidx>
|
||||||
|
@ -569,7 +721,8 @@ an information central for documentation, project pages and much, much more.
|
||||||
Please let me know if you have any other leads that can be of interest.
|
Please let me know if you have any other leads that can be of interest.
|
||||||
|
|
||||||
|
|
||||||
<sect>Getting Help
|
<sect>GETTING HELP
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<nidx>(your index root)!assistance, obtaining</nidx>
|
<nidx>(your index root)!assistance, obtaining</nidx>
|
||||||
|
|
||||||
|
|
|
@ -46,7 +46,7 @@ Vi Improved with syntax color highlighting
|
||||||
"name="
|
"name="
|
||||||
alavoor@yahoo.com
|
alavoor@yahoo.com
|
||||||
">
|
">
|
||||||
<date>v12.0, 10 July 2000
|
<date>v13.0, 07 Aug 2000
|
||||||
<abstract>
|
<abstract>
|
||||||
This document is a guide to quickly setting up the Vim color editor on Linux or Unix systems. The information here will improve the productivity of programmers because the
|
This document is a guide to quickly setting up the Vim color editor on Linux or Unix systems. The information here will improve the productivity of programmers because the
|
||||||
Vim editor supports syntax color highlighting and bold fonts, improving the
|
Vim editor supports syntax color highlighting and bold fonts, improving the
|
||||||
|
@ -777,6 +777,55 @@ The best background color is lightyellow or white, with black foreground.
|
||||||
-->
|
-->
|
||||||
<sect> Color Syntax init files
|
<sect> Color Syntax init files
|
||||||
<p>
|
<p>
|
||||||
|
<sect1> Auto source-in method
|
||||||
|
<p>
|
||||||
|
This section below is obtained from gvim session by typing 'help syntax' -
|
||||||
|
<code>
|
||||||
|
bash$ gvim some_test
|
||||||
|
:help syntax
|
||||||
|
</code>
|
||||||
|
And then do CTRL+T on 'Syntax Loading Procedure' menu which will take you there.
|
||||||
|
|
||||||
|
If a file type that you want to use is not detected yet, there are two ways to
|
||||||
|
add it. It's better not modify the <it>$VIMRUNTIME/filetype.vim</it> file. It will be
|
||||||
|
overwritten when installing a new version of Vim.
|
||||||
|
Create a file in $HOME/vim/myfiletypes.vim and put these line in it -
|
||||||
|
<code>
|
||||||
|
" Filename : $HOME/vim/myfiletypes.vim
|
||||||
|
" myfiletypefile
|
||||||
|
augroup filetype
|
||||||
|
au! BufRead,BufNewFile *.mine set filetype=mine
|
||||||
|
au! BufRead,BufNewFile *.xyz set filetype=drawing
|
||||||
|
au! BufRead,BufNewFile *.prc set filetype=plsql
|
||||||
|
augroup END
|
||||||
|
</code>
|
||||||
|
|
||||||
|
Then add a line in your $HOME/.vimrc and $HOME/.gvimrc file to set the "myfiletypefile" variable to
|
||||||
|
the name of this file. (<bf>CAUTION:</bf> You MUST put this in both vimrc and gvimrc files
|
||||||
|
in order for this to work) Example:
|
||||||
|
<code>
|
||||||
|
let myfiletypefile = "~/vim/myfiletypes.vim"
|
||||||
|
</code>
|
||||||
|
|
||||||
|
<bf>NOTE:</bf> Make sure that you set "myfiletypefile" before switching on file type
|
||||||
|
detection. This is must be before any ":filetype on" or ":syntax on"
|
||||||
|
command.
|
||||||
|
|
||||||
|
Your file will then be sourced after the default FileType autocommands have
|
||||||
|
been installed. This allows you to overrule any of the defaults, by using
|
||||||
|
":au!" to remove any existing FileType autocommands for the same pattern.
|
||||||
|
Only the autocommand to source the scripts.vim file is given later. This
|
||||||
|
makes sure that your autocommands in "myfiletypefile" are used before
|
||||||
|
checking the contents of the file.
|
||||||
|
<!--
|
||||||
|
*******************************************
|
||||||
|
************ End of Section ***************
|
||||||
|
*******************************************
|
||||||
|
|
||||||
|
|
||||||
|
-->
|
||||||
|
<sect1> Manual method
|
||||||
|
<p>
|
||||||
Instead of using "Syntax" menu you can also
|
Instead of using "Syntax" menu you can also
|
||||||
manually source in the syntax file. Edit the file with gvim
|
manually source in the syntax file. Edit the file with gvim
|
||||||
and at : (colon) command give 'so' command. For example -
|
and at : (colon) command give 'so' command. For example -
|
||||||
|
|
Loading…
Reference in New Issue