On Tue, Sep 06, 2022 at 10:43:50PM +, Tim Chase wrote:
> On 2022-09-06 14:45, andalou wrote:
> > I have the table:
> > 1001 john sena 4
> > 1002 jafar iqbal 6
> > 1003 meher nigar 3
> > 1004 jonny liver 7
> > I'd like to print the first field, preceded by xx, and followed
Den fre 9 sep. 2022 10:50Jirka Novak skrev:
> Hi,
>
>I'm maintaining set of docker containers. We use convention that
> every config file for a container is in /srv// subdirectory.
> E.g. /srv//etc/cron.daily/logrotate.
>We use vim to maintain config files and we like feature/shortcut
Take a look at Windows Event Viewer. You may be able to glean something
from that.
Do you have an antivirus program running?
--
--
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
hi,
On Fri, 9 Sept 2022 at 12:39, A. S. Budden wrote:
> ...
>> I tried removing the HOME environment variable from cygwin (it's not set to
>> anything in the Windows system, whereas it's set to /home/al in cygwin) and
>> ran the command again from the cygwin terminal and it took a long time to
On Fri, 9 Sept 2022 at 12:06, A. S. Budden wrote:
> On Thu, 8 Sept 2022, 19:29 Gary Johnson, wrote:
>
>> On 2022-09-08, David Lowry-Duda wrote:So if I run Windows gvim from a
>> cygwin terminal it starts quickly but if I run it from a windows command
>> prompt or from windows explorer, it takes
On Thu, 8 Sept 2022, 19:29 Gary Johnson, wrote:
> On 2022-09-08, David Lowry-Duda wrote:
> > >I'm pretty sure it's something about my configuration / plugins /
> > >something (gvim -u NONE -U NONE takes about 5 seconds), but I'm
> > >really struggling to diagnose the issue / work out which
On Thu, 8 Sept 2022, 19:38 Tim Chase, wrote:
> On 2022-09-08 11:30, Gary Johnson wrote:
> > I suspect that whatever is causing that 5-second startup time is
> > contributing to the read times of every file that gvim opens.
> > So, while 5 seconds is better than 30, solving that 5-second issue
>
Hi,
I'm maintaining set of docker containers. We use convention that
every config file for a container is in /srv// subdirectory.
E.g. /srv//etc/cron.daily/logrotate.
We use vim to maintain config files and we like feature/shortcut 'gf'
which opens file on cursor. E.g. logrotate file
Problem solved,
* john magolske [220905 14:14]:
> after upgrading my debian system from buster to bullseye (vim 8.1 to
> 8.2), i'm seeing a noticeably longer start time for vim, about 5-6
> seconds. i tried:
>
> vim --startuptime vim.log
>
> and looking at that vim.log file it seems
