On 2022-07-19, Kutty, Rejeesh wrote:
> Hi,
>
> I recently ran the installer and it updated vim to 8.2
>
> :version
> VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Feb 13 2022 22:00:24)
> Included patches: 1-4372
>
>
> Now when I open a perl script, I get the following message:
>
> Command termi
Hi,
I recently ran the installer and it updated vim to 8.2
:version
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Feb 13 2022 22:00:24)
Included patches: 1-4372
Now when I open a perl script, I get the following message:
Command terminated
Error detected while processing BufRead Autocommands
Thank you very much. It works.
---
From:
Fxzx mic
fxzx...@outlook.com<mailto:fxzx...@outlook.com>
---
发件人: Brian Inglis<mailto:brian.ing...@systematicsw.ab.ca>
发送时间: 2021年6月28日 3:25
收件人: cygwin@cygwin.com<mailto:cygwin@cygwin.com>
主题: Re: A warning about GVIM
On 2021-06-27 07:
On 2021-06-27 07:51, ㅤ Fxzx mic via Cygwin wrote:
I have such a warning:
** (gvim:1682): WARNING **: Error retrieving accessibility bus address:
org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message
bus without replying
Can this be fixed?
Please read the previous
Hello, everyone.
I have such a warning:
** (gvim:1682): WARNING **: Error retrieving accessibility bus address:
org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message
bus without replying
Can this be fixed?
---
From:
Fxzx mic
fxzx...@outlook.com<mailto:f
On 2021/04/08 04:19, Andrey Repin wrote:
It has it in every version starting Windows 95/NT4.
@Linda: try http://joelpurra.com/Projects/X-Mouse_Controls/
---
Just had the occasion to need it, since had to re-inst W7.
Unfortunately, it immediately dumps core. Very odd.
Dependency walker tries
> ** (gvim:1682): WARNING **: Error retrieving accessibility bus address:
> org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from
> message bus without replying
>
> Can this be fixed?
I get the same warning from gvim, emacs, zenity, and gitg.
--
Problem repo
On 15.06.2021 03:10, Claude Sylvain wrote:
On 2021-06-14 3:23 a.m., Fxzx mic via Cygwin wrote:
** (gvim:1682): WARNING **: Error retrieving accessibility bus
address: org.freedesktop.DBus.Error.NoReply: Message recipient
disconnected from message bus without replying
Can this be fixed
On 2021-06-14 3:23 a.m., Fxzx mic via Cygwin wrote:
** (gvim:1682): WARNING **: Error retrieving accessibility bus address:
org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message
bus without replying
Can this be fixed?
---
From:
Fxzx mic
fxzx...@outlook.com
Andrey Repin writes:
>> Windows never had "focus follows mouse" in any version I can remember.
>
> It has it in every version starting Windows 95/NT4.
The last time I tried it it didn't quite work, though. Specifically it
does "focus strictly follows mouse" and it had problems with raising
unwant
to really do
it would be along the lines of detecting when windows had grabbed
control via its time -- for cygwin to use a timer to detect when it
lost control. Ex. in cygwin's blink routine, it would need to check
There is no 'cygwin blink routine' - this is something that the X clie
detecting when windows had grabbed
control via its time -- for cygwin to use a timer to detect when it
lost control. Ex. in cygwin's blink routine, it would need to check
There is no 'cygwin blink routine' - this is something that the X client
(e.g. gvim in your example) is doing
On 09/04/2021 16:12, Thomas Wolff wrote:
See [1] et seq. for a discussion of what I think is the same problem,
where the Cygwin X server doesn't notify X windows of a focus loss
when the focus moves to a non-X window.
Hmm, when I start xterm -bc and click out of xterm (e.g. mintty or
Thunderb
On 2021/04/09 08:12, Thomas Wolff wrote:
Hmm, when I start xterm -bc and click out of xterm (e.g. mintty or
Thunderbird), the cursor stops blinking for me.
---
That's the key difference "click out of xterm" -- in pointer follows
focus, no clicking is used. The active window becomes the one u
On 2021/04/10 12:14, L A Walsh wrote:
On 2021/04/09 07:41, Jon Turney wrote:
I think so, yes.
===
That's unfortunate. Well, I wasn't sure if it was new
or old. At least its not some new problem. Sigh.
Thanks for the backstory.
[1] https://sourceware.org/legacy-ml/
On 2021/04/09 07:41, Jon Turney wrote:
I think so, yes.
===
That's fine, I guess I hadn't noticed it before --
had about 3-X and maybe 2 native and couldn't figure out why I
occasionally had typing going to the wrong window when I realized I
had been relying on the blinking for the a
Am 09.04.2021 um 16:41 schrieb Jon Turney:
On 07/04/2021 01:27, L A Walsh wrote:
I don't recall this always being this way as I keep running into
a problem with my input going into the wrong window.
I've noted I seem to be relying on which editor(i.e. gvim)
window in X11 has focus
On 07/04/2021 01:27, L A Walsh wrote:
I don't recall this always being this way as I keep running into
a problem with my input going into the wrong window.
I've noted I seem to be relying on which editor(i.e. gvim)
window in X11 has focus by noting that it has a
blinking square cur
Greetings, Achim Gratz!
> L A Walsh writes:
>> If I move the windows cursor to another editor window in X11,
>> the blinking cursor moves to the new window, but if I move
>> it to a native window, the blinking doesn't stop.
>>
>> Has this always been this way?
> Windows never had "focus follows m
On April 7, 2021 8:47 PM Achim Gratz wrote:
>L A Walsh writes:
>> If I move the windows cursor to another editor window in X11,
>> the blinking cursor moves to the new window, but if I move
>> it to a native window, the blinking doesn't stop.
>>
>> Has this always been this way?
>
>Windows never ha
On 2021/04/07 11:46, Achim Gratz wrote:
L A Walsh writes:
If I move the windows cursor to another editor window in X11,
the blinking cursor moves to the new window, but if I move
it to a native window, the blinking doesn't stop.
Has this always been this way?
Windows never had "focus
L A Walsh writes:
> If I move the windows cursor to another editor window in X11,
> the blinking cursor moves to the new window, but if I move
> it to a native window, the blinking doesn't stop.
>
> Has this always been this way?
Windows never had "focus follows mouse" in any version I can remembe
I don't recall this always being this way as I keep running into
a problem with my input going into the wrong window.
I've noted I seem to be relying on which editor(i.e. gvim)
window in X11 has focus by noting that it has a
blinking square cursor in the window at the cursor's
c
On 2020-09-09 00:55, L A Walsh wrote:
> I was trying to edit files in
> /etc/ssh:
> /etc/ssh> gvim sshd_config
>
> Error: Current working directory has restricted permissions which render it
>
> inacc
I was trying to edit files in
/etc/ssh:
/etc/ssh> gvim sshd_config
Error: Current working directory has restricted permissions which render it
inaccessible as Win32 working direct
The latest Vim/GVim package currently available on Cygwin Packages has
broken ruby support.
Here is the stackoverflow question about the same:
https://stackoverflow.com/questions/47356294/cygwin-installing-vim-with-ruby-support
and here is the short list of the status of ruby support on Vim.
vim
I installed Cygwin yesterday and I am unable to startup GVIM in a
separate window. I verified Xwin is running and I tried a few
different types of DISPLAY;
:0
:0;0
localhost:0.0 (with the XWin server started with -listen inet)
All failed with the following errors:
Vim: Caught deadly signal SEGV
I have an issue running gvim (under X11) where subprocesses invoked
with the bang command will hang.
For example, I might run:
! git pull
and the process will never complete. If I look at task manager, I will
see a gvim.exe subprocess with around 30% CPU occupying the top of the
CPU usage on
>
> Yes, I tried it for both PC-based gvim and Cygwin gvim on X11. Both
> work. However, at the time, clicking middle button also worked in
> pasting into gvim. I will have to try again when middle button
> doesn't work.
OK - I only use the normal GVim commands for yanki
Alan Thompson gmail.com> writes:
> Everything I said works both ways, both Cygwin->Windoze and
> Windoze->Cygwin. The only difference in GVim is whether you use
> yank
> ("Y") or put ("P"). This works for both the win32 version of GVim
> and
>
On Wed, Jan 23, 2013 at 11:58 PM, Andy wrote:
>
> Guys, thanks for your replies. I might not have been clear enough in
> my original post, but the problem is in attempting to copy from a
> Windows app and pasting into Cygwin's gvim. Correct me if I'm wrong,
> but you
Chris Sutcliffe gmail.com> writes:
|On 22 January 2013 11:55, Andy wrote:
|> I installed cygwin's gvim on Windows 7. I found that pasting from
|> the Windows clipboard into gvim doesn't work by clicking the middle
|> mouse button unless I go through a weird ritual t
doze app (browser, etc) using Crtl-V as usual
Also, note that for some things I use the Cygwin version of GVim (have
to start the X11 server first), and for some things I use the native
Windows version of GVim.
Alan Thompson
On Tue, Jan 22, 2013 at 9:18 AM, Chris Sutcliffe wrote:
> On 22 Janu
On Tue, Jan 22, 2013 at 11:55 AM, Andy wrote:
>
> I installed cygwin's gvim on Windows 7. I found that pasting from the
> Windows clipboard into gvim doesn't work by clicking the middle mouse
> button unless I go through a weird ritual that I discovered by
> accident.
On 22 January 2013 11:55, Andy wrote:
> I installed cygwin's gvim on Windows 7. I found that pasting from the
> Windows clipboard into gvim doesn't work by clicking the middle mouse
> button unless I go through a weird ritual that I discovered by
> accident. If I don&
I installed cygwin's gvim on Windows 7. I found that pasting from the
Windows clipboard into gvim doesn't work by clicking the middle mouse
button unless I go through a weird ritual that I discovered by
accident. If I don't do this, I get "E353: Nothing in register *
I installed cygwin's gvim on Windows 7. I found that pasting from the
Windows clipboard into gvim doesn't work by clicking the middle mouse
button unless I go through a weird ritual that I discovered by
accident. If I don't do this, I get "E353: Nothing in register *
On Sun, Aug 05, 2012 at 12:34:25AM -0400, ping wrote:
>folks/experts:
>I just successfully recompiled vim with GUI support under cygwin.
>so now gvim is OK if I launch it from cygwin terminal (yes I have X running)
>then I'm trying to make it the default text editor for my wind
folks/experts:
I just successfully recompiled vim with GUI support under cygwin.
so now gvim is OK if I launch it from cygwin terminal (yes I have X running)
then I'm trying to make it the default text editor for my window7
application
(like outlook, to open attachment), but then I got a d
This morning, I reverted GLib2.0 to a previous version and it did not
solve the issue.
Steps used in testing:
Extracted "libglib2.0_0-2.30.2-1.tar.bz2" and ran /etc/postinstall/glib2.0.sh
Started XWin and attempted to edit a file via gvim (performance issue
still remain)
On Fri, Jun 1,
On 6/1/2012 7:00 AM, Ken Brown wrote:
I found an XP system that hadn't been upgraded in a few weeks, and I
upgraded libglib2.0_0 but nothing else. This was enough to trigger the
problem.
I've checked the git repository for glib at
http://git.gnome.org/browse/glib/log/?h=glib-2-32
and there
Ken Brown cornell.edu> writes:
> Fortunately for emacs users, the problem doesn't seem to occur with
> emacs-24. (Can anyone else confirm this?)
Hi Ken,
So I just upgraded to emacs-24 (24.0.96.1), and while it is certainly better, I
wouldn't say it's fixed.
Try opening a text file (I have a ~
to switch to the *scratch* buffer.
4. Press and hold one key. It echoes once, but the "repeated" key strokes
don't get echoed until you release the key.
Fortunately for emacs users, the problem doesn't seem to occur with
emacs-24. (Can anyone else confirm this?) But that
t Menu shortcut.
>
> 2. Install emacs-X11-23.4-2, and start emacs under X.
>
> 3. Type 'C-x b RET' to switch to the *scratch* buffer.
>
> 4. Press and hold one key. It echoes once, but the "repeated" key strokes
> don't get echoed until you release th
et echoed until you release the key.
Fortunately for emacs users, the problem doesn't seem to occur with
emacs-24. (Can anyone else confirm this?) But that doesn't help the
gvim users who have reported similar problems.
Yaakov, could you take a look? Maybe you could also make th
Mon, May 14, 2012 at 02:55PM -0400 K Stahl wrote:
> What I am witnessing is that if you hold down any of these keys, the
> cursor remains in place until the key is released.
I'm seeing about the same think in emacs-X11.
I hold down an arrow key and the cursor stays still until I release
it a
Modified from my original email on the XFree mailing list:
After updating yesterday (2012-05-10) I am experiencing the following
behavior when using GVim within an X-Session:
While scrolling through a file in visual mode using either "H", "J",
"K", or "L"
On 2012-02-06, reckoner wrote:
> Hi,
>
> I usually start the non-cygwin gvim.exe via the rxvt cygwin console
> doing something like:
>
> % gvim filename.py
>
> the problem is that, when inside GVIM, when I do:
>
> :py print os.environ['PATH']
>
&g
On Mon, Feb 06, 2012 at 01:04:28PM -0800, reckoner wrote:
>Hi,
>
>I usually start the non-cygwin gvim.exe via the rxvt cygwin console
>doing something like:
>
>% gvim filename.py
>
>the problem is that, when inside GVIM, when I do:
>
>:py print os.environ['PA
Hi,
I usually start the non-cygwin gvim.exe via the rxvt cygwin console
doing something like:
% gvim filename.py
the problem is that, when inside GVIM, when I do:
:py print os.environ['PATH']
I see a lot of cygwin paths which messes up the Python path that GVIM
wants to use.
Saxon, Will sage.com> writes:
>
> My script works, but if I do run it from a command window it generates a stack
dump:
>
> Exception: STATUS_GUARD_PAGE_VIOLATION at eip=61020137
I had a similar problem, what fixed it for me was to move /cygwin to
/cygwin.save and re-install cygwin.
Lee
--
ct2: ld returned 1 exit status
> make: *** [gvim.exe] Error 1
see
http://cygwin.com/ml/cygwin/2011-05/msg00369.html
>
> I'd be grateful for advice on compiling gvim under cygwin to work as a
> Windows application.
As you are building a standalone version of
gt; vim.exe
7 May 30 02:45 vimdiff -> vim.exe
12288 May 30 02:45 xxd.exe
I'd be grateful for advice on compiling gvim under cygwin to work as a Windows
application.
Regards,
Clyde
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq
On Tue, 2011-03-01 at 01:08 +0100, Paul Maier wrote:
> Hi,
>
> my gvim dies when I select file->open from gvim's menu (see screenshot in
> file gvim.jpg.uuencode.txt).
> 100 % reproducable.
> Same, if I start gvim with a file to edit or without.
WFM. How are y
Hello,
I am trying to run gvim via Cygwin using run.exe and a shell script. The reason
I am doing this is so that I can assign the command to a button vs. opening
gvim from a shell.
My script works, but if I do run it from a command window it generates a stack
dump:
Exception
Hi,
I can't get gVim to work using X forwarding over SSH. Both xeyes and
xemacs work fine, but not gVim. gVim works when running it locally,
but gets a deadly signal when trying to run it from an SSH connection.
Any and all help would be greatly appreciated!
Here is some relevant console o
2009/12/4 Christopher Faylor:
>>Hang on, if I do this:
>>
>>$ setsid gvim -display :0 &
>>
>>in a bash console and then close the console, gvim continues to work,
>>so either setsid or gvim itself does detach from the console.
>
> That makes sense.
gt;>> a free and clear process (unaffected by bash exiting).
>>>
>>> Yet when I exit the bash window (bash running in a console window), Gvim
>>> is killed. ??Why should bash or the console exiting kill off any processes
>>> running in the background?
>>
; Yet when I exit the bash window (bash running in a console window), Gvim
>> is killed. Why should bash or the console exiting kill off any processes
>> running in the background?
>
> Were you closing the console window by pressing the close button?
>
> In that case, the pr
ng in a console window), Gvim
> is killed. Why should bash or the console exiting kill off any processes
> running in the background?
Were you closing the console window by pressing the close button?
In that case, the problem is that gvim is built as a console program,
which means that it
), Gvim
is killed. Why should bash or the console exiting kill off any processes
running in the background?
I have had the same frustration for a while. When in a bash shell start
gvim with:
cmd /c gvim
then you can exit the bash shell without killing gvim.
FWIW:
I am using gvim v7.0 for 32bit MS
t as desirable if it does this correction
"silently".
Yeah...
Probably not that here, but whatever. It's probably still true with x
progs, but they aren't where I left them. (gvim in particular)...
That's what I'm talking about -- things appear to show up in some
locat
In bash I start a copy of gvim.exe (64-bit windows version) in background.
I disown the job in bash so bash no longer manages the job -- it should be
a free and clear process (unaffected by bash exiting).
Yet when I exit the bash window (bash running in a console window), Gvim
is killed. Why
On Fri, Sep 25, 2009 at 10:30:33AM +0200, Angelo Graziosi wrote:
>Christopher Faylor wrote:
>> To clarify: I see nothing in any of the chain of messages that you
>> referred to which indicates that this is the same problem. You're
>> asserting that this is the case but not providing any details t
On 9/25/2009 4:53 AM, Angelo Graziosi wrote:
If you want a 'native' 1.7 build, I can write how I do (mainly
configure+make+make install). However, the current method used by Ken
(the Emacs maintainer) should be valid if one remove 'lucid' and uses
'gtk' to obtain a GTK build.
Yes, that works.
Yaakov (Cygwin/X) wrote:
Could you put your emacs-gtk tarballs somewhere, or if not, at least your
.cygport?
Yaakov,
I still do not use cygport to build Emacs. :-(
In any case, I have a Cygwin-1.5 build here(*) for Emacs-23 with which
the problems I flagged are reproducible (at least by me)
Christopher Faylor wrote:
To clarify: I see nothing in any of the chain of messages that you
referred to which indicates that this is the same problem. You're
asserting that this is the case but not providing any details to
back that statement up.
I *think* (my guess) it is the same problem b
On 24/09/2009 19:39, Angelo Graziosi wrote:
In my case(*), using 20090924 snapshot, it fixes the problem partially:
Emacs hangs on quitting.
Could you put your emacs-gtk tarballs somewhere, or if not, at least
your .cygport?
Yaakov
--
Problem reports: http://cygwin.com/problems.html
On Thu, Sep 24, 2009 at 09:30:34PM -0400, Christopher Faylor wrote:
>On Fri, Sep 25, 2009 at 02:39:38AM +0200, Angelo Graziosi wrote:
>>Cesar Strauss wrote:
>>> Christopher Faylor wrote:
If you could test this and confirm that the snapshot fixes the problem I'll
roll a new release. It t
On Fri, Sep 25, 2009 at 02:39:38AM +0200, Angelo Graziosi wrote:
>Cesar Strauss wrote:
>> Christopher Faylor wrote:
>>> If you could test this and confirm that the snapshot fixes the problem I'll
>>> roll a new release. It turns out to be a pretty serious bug.
>>>
>>> http://cygwin.com/snapshots
Cesar Strauss wrote:
Christopher Faylor wrote:
If you could test this and confirm that the snapshot fixes the problem I'll
roll a new release. It turns out to be a pretty serious bug.
http://cygwin.com/snapshots/
I am not the OP, but I could reproduce the problem, and I confirm it is
fixed
On Mon, Sep 21, 2009 at 06:42:18PM -0500, Yaakov (Cygwin/X) wrote:
>On 21/09/2009 09:48, Christopher Faylor wrote:
>> gdb said that the failure was coming from libxcb-1.dll so I rebuilt
>> libxcb-1.dll with debugging information and with a version of
>> libcygwin.a containing debugging symbols.
>
>
On 21/09/2009 09:48, Christopher Faylor wrote:
gdb said that the failure was coming from libxcb-1.dll so I rebuilt
libxcb-1.dll with debugging information and with a version of
libcygwin.a containing debugging symbols.
Wait, did I just hear an argument for split debug packages? :-)
The fix fo
On Mon, Sep 21, 2009 at 05:13:39PM +0100, Dave Korn wrote:
>Christopher Faylor wrote:
>>I can say that any DLL built with cygwin-1.7.0-51 - cygwin-1.7.0-56 is
>>probably suspect. That's 2009-07-13 - 2009-08-13 .
>
>Argh, that's my fault isn't it? Sorry for not figuring out we should
>have done th
Christopher Faylor wrote:
> I can say that any DLL built with cygwin-1.7.0-51 - cygwin-1.7.0-56
> is probably suspect. That's 2009-07-13 - 2009-08-13 .
Argh, that's my fault isn't it? Sorry for not figuring out we should have
done this when we first fixed that bug and thanks for putting in th
On Mon, Sep 21, 2009 at 02:51:50AM -0500, Yaakov (Cygwin/X) wrote:
>On 20/09/2009 21:24, Christopher Faylor wrote:
>>This should be fixed in the next Cygwin snapshot and, subsequently, in
>>the next release.
>>
>>If you could test this and confirm that the snapshot fixes the problem
>>I'll roll a n
On 20/09/2009 21:24, Christopher Faylor wrote:
This should be fixed in the next Cygwin snapshot and, subsequently, in the
next release.
>
If you could test this and confirm that the snapshot fixes the problem I'll
roll a new release. It turns out to be a pretty serious bug.
For me this fixe
Christopher Faylor wrote:
On Sat, Sep 12, 2009 at 04:14:11PM +0200, Fr??d??ric Bron wrote:
I believe it worked fine before (until a few days ago). I updated to
latest cygwin by running setup-1.7.exe.
(Just running setup -> click several next... ??-> finish)
And now if I do
?? ??/bi
> finish)
>>>
>>> And now if I do
>>> ?? ??/bin/gvim
>>> ?? ??:!ls
>>>
>>> I see a message 'Cannot fork' in the gvim window.
>>> And see
>>> ?? ??2 [main] gvim 2092 fork: child -1 - died waiting for longjmp
>>>
On Sat, Sep 12, 2009 at 04:14:11PM +0200, Fr??d??ric Bron wrote:
>> I believe it worked fine before (until a few days ago). I updated to
>> latest cygwin by running setup-1.7.exe.
>> (Just running setup -> click several next... ??-> finish)
>>
>> And now if
> I believe it worked fine before (until a few days ago). I updated to
> latest cygwin by running setup-1.7.exe.
> (Just running setup -> click several next... -> finish)
>
> And now if I do
> /bin/gvim
> :!ls
>
> I see a message 'Cannot fork'
On 06/29/2009, tsunhin wong wrote:
904k 2002/10/14 C:\Lens\Bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
"cygwin1.dll" v0.0 ts=2002/10/13 23:15
Delete this old copy of 'cygwin1.dll' and try again.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc.
Another program that use console output SBCL.exe display correctly in
both cmd.exe and bash.exe
I have no idea why vim.exe cannot work on this Vista cygwin setting.
I'm including my cygcheck.out, I hope someone can really help, thank in advance!
- J
Cygwin Configuration Diagnostics
Current Syste
Buchbinder, Barry (NIH/NIAID) [E] wrote:
Linda Walsh sent the following at Monday, June 29, 2009 2:12 AM
Any reason not to run the Win32-Gvim native client
Linda (or anyone who has an answer):
Do you have any suggestions for commands that should be put in _vimrc
so using cygwin is
with the following settings:
>
> - gVim 7.2 installed with vim.exe
> - set PATH in environmental variables to include C:\Program files\Vim\vim72
> - set .vimrc to point to _vimrc
> - ln -s vim.exe /usr/bin/vi
>
> In my XP, I can trigger vim in my cygwin windows by typing "vi&
tsunhin wong wrote:
Hi all,
I am trying to run vim inside my cygwin shell in Vista
I've done it successfully in XP with the following settings:
- gVim 7.2 installed with vim.exe
- set PATH in environmental variables to include C:\Program files\Vim\vim72
- set .vimrc to point to _vimrc
-
Linda Walsh sent the following at Monday, June 29, 2009 2:12 AM
> Any reason not to run the Win32-Gvim native client?
Linda (or anyone who has an answer):
Do you have any suggestions for commands that should be put in _vimrc
so using cygwin is transparent? I am especially concerned w
Hi all,
I am trying to run vim inside my cygwin shell in Vista
I've done it successfully in XP with the following settings:
- gVim 7.2 installed with vim.exe
- set PATH in environmental variables to include C:\Program files\Vim\vim72
- set .vimrc to point to _vimrc
- ln -s vim.exe /usr/b
Yanroy wrote:
Hi all... the subject line pretty much says it all. I've installed Cygwin
and Cygwin/X. The X server appears to work correctly. XTerm runs fine.
All the command-line apps work great. When I launch gvim, it spins for a
moment and then crashes with an access viol
Yanroy wrote:
Hi all... the subject line pretty much says it all. I've installed Cygwin
and Cygwin/X. The X server appears to work correctly. XTerm runs fine.
All the command-line apps work great. When I launch gvim, it spins for a
moment and then crashes with an access violation. No
Hi all... the subject line pretty much says it all. I've installed Cygwin
and Cygwin/X. The X server appears to work correctly. XTerm runs fine.
All the command-line apps work great. When I launch gvim, it spins for a
moment and then crashes with an access violation. Nothing is writt
Corinna Vinschen wrote
If that doesn't work, try rebasing:
$ less /usr/share/doc/Cygwin/rebase-3.0.README
Ugh. I followed the instructions and did rebaseall and peflagsall. It fixed
gvim, but broke other things like this:
perl 2084 F:\cygwin\bin\perl.exe: *** fatal error - unable to
Corinna Vinschen wrote:
If that doesn't work, try rebasing:
$ less /usr/share/doc/Cygwin/rebase-3.0.README
Thank you. The latest cygwin dll did not help but rebasing fixed it.
- Ian Kelling
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/fa
On Jun 22 03:12, Ian Kelling wrote:
> from xterm I get 2 errors. They are inconsistent, but one or the other
> seems to happen within 1 or 2 starts of gvim.
>
> It continues to run after this one.
> $ /bin/gvim
> 2 [main] gvim 5804 child_copy: linked dll data write copy
from xterm I get 2 errors. They are inconsistent, but one or the other seems
to happen within 1 or 2 starts of gvim.
It continues to run after this one.
$ /bin/gvim
2 [main] gvim 5804 child_copy: linked dll data write copy failed,
0x2B7000..0x2B76CC, done 0, windows pid 6048, Win32 error
more days it would have been a bit funnier.
>
>>> On Tue, Jan 29 2008, Shai wrote:
>>>
>>> > Hi,
>>> >
>>> > I have gvim installed and when I do:
>>> > $ crontab -e
>>> > gvim opens up my crontab.
>>> >
>&
29 2008, Shai wrote:
>>
>> > Hi,
>> >
>> > I have gvim installed and when I do:
>> > $ crontab -e
>> > gvim opens up my crontab.
>> >
>> > But, it opens it as readonly and saving it requires wq! but then when
>> > it e
On 2009-01-27, Shai wrote:
> On Tue, Jan 29, 2008 at 9:42 PM, Toby Allsopp wrote:
> >
> > On Tue, Jan 29 2008, Shai wrote:
> > > I have gvim installed and when I do:
> > > $ crontab -e
> > > gvim opens up my crontab.
> > >
> > > But,
On Tue, Jan 29, 2008 at 9:42 PM, Toby Allsopp wrote:
>
> On Tue, Jan 29 2008, Shai wrote:
>
> > Hi,
> >
> > I have gvim installed and when I do:
> > $ crontab -e
> > gvim opens up my crontab.
> >
> > But, it opens it as readonly and savin
I cannot seem to get the Cygwin gvim-7.2 to print to my HP Officejet.
I keep getting
E365: Failed to print Postscript file.
However, I have also installed from ftp.vim.org//pub/vim/pc that version
of gvim-7.2 under Program Files and I can print just file from that gvim.
Thanks.
Lester
1 - 100 of 189 matches
Mail list logo
