thout argument) when you do not set colorscheme in init files. Is it
"default"?
to get rid of the message, I replaced the vi binary by a script where
stderr is redirected to /dev/null
I would say it is quite rude. You may miss a message notifying you that
you have some typo in a c
On 12/23/22, Thomas Schmitt wrote:
> Hi,
>
> Curt wrote:
>> You'd think it would be more a question of the terminal.
>
> I myself am living happily with
> :syntax off
>
> This reduces the flippy-colorful appearance of vim to what i have chosen
> as -bg and -fg of my xterms.
I used to agree with
On Fri, 23 Dec 2022, Curt wrote:
On 2022-12-23, Nate Bargmann wrote:
Because there is no colorscheme named "white" in Debian's
vim. The colorschemes are in /usr/share/vim/vim82/colors
The problem as I see it is that he wants reverse colors in 'vi' but
edited
On 2022-12-23, Nate Bargmann wrote:
>
>> >
>> > The problem as I see it is that he wants reverse colors in 'vi' but
>> > edited '.vimrc'. Historically those are two different programs but the
>> > Debian alternatives eventually point
* On 2022 23 Dec 13:03 -0600, Curt wrote:
> On 2022-12-23, Nate Bargmann wrote:
> >
> >> Because there is no colorscheme named "white" in Debian's
> >> vim. The colorschemes are in /usr/share/vim/vim82/colors
> >
> > The problem as I see it
Hi,
Curt wrote:
> You'd think it would be more a question of the terminal.
I myself am living happily with
:syntax off
This reduces the flippy-colorful appearance of vim to what i have chosen
as -bg and -fg of my xterms.
Have a nice day :)
Thomas
On 2022-12-23, Nate Bargmann wrote:
>
>> Because there is no colorscheme named "white" in Debian's
>> vim. The colorschemes are in /usr/share/vim/vim82/colors
>
> The problem as I see it is that he wants reverse colors in 'vi' but
> edited '.
On 2022-12-23, David wrote:
>>
>> You could try using a different colorscheme. Apparently, there's no
>> way to get vim to tell you their names,
>
> To see the available colorschemes, do this in vim:
>:colorscheme
>
>
I have: blue, darkblue, default, delek, desert, elflord, evening,
industry, ko
On Fri, 23 Dec 2022, Max Nikulin wrote:
On 23/12/2022 18:36, Pierre Frenkiel wrote:
I wanted to open vi with a white background and a black fg
to do that,
Do you mean graphical gvim window or vim running in a terminal? In the latter
case which one and should vim follow terminal background
* On 2022 23 Dec 06:54 -0600, David wrote:
> On Fri, 23 Dec 2022 at 23:31, Greg Wooledge wrote:
> > On Fri, Dec 23, 2022 at 12:36:56PM +0100, Pierre Frenkiel wrote:
>
> > > I wanted to open vi with a white background and a black fg
> > > to do that, I put in my
On 23/12/2022 18:36, Pierre Frenkiel wrote:
I wanted to open vi with a white background and a black fg
to do that,
Do you mean graphical gvim window or vim running in a terminal? In the
latter case which one and should vim follow terminal background? Is tmux
or screen involved?
Besides
On Fri, 23 Dec 2022 at 23:31, Greg Wooledge wrote:
> On Fri, Dec 23, 2022 at 12:36:56PM +0100, Pierre Frenkiel wrote:
> > I wanted to open vi with a white background and a black fg
> > to do that, I put in my .vimrc, as recommended, a line
> > colorscheme white
&qu
On Fri, Dec 23, 2022 at 07:31:14AM -0500, Greg Wooledge wrote:
> On Fri, Dec 23, 2022 at 12:36:56PM +0100, Pierre Frenkiel wrote:
> > I wanted to open vi with a white background and a black fg
> > to do that, I put in my .vimrc, as recommended, a line
> > colorscheme
On Fri, Dec 23, 2022 at 12:36:56PM +0100, Pierre Frenkiel wrote:
> I wanted to open vi with a white background and a black fg
> to do that, I put in my .vimrc, as recommended, a line
> colorscheme white
> that worked, except that each time I open vim, I get the message:
>ca
hi,
I wanted to open vi with a white background and a black fg
to do that, I put in my .vimrc, as recommended, a line
colorscheme white
that worked, except that each time I open vim, I get the message:
cannot find color scheme 'white'
I don't worry, but is there a way to
Med venlig hilsen
Lasse Carlsen
Start på videresendt besked:
> Sendt igen-Fra: debian-user@lists.debian.org
> Fra: "Filippa Brouage"
> Dato: 13. juli 2017 kl. 10.11.04 CEST
> Til: debian-user@lists.debian.org
> Emne: Hvad er det bedste remedie for det vi snakk
On 07/04/2016 08:51 PM, Gary Dale wrote:
There seems to be a combination of keystrokes that I accidentally hit
from time to time that puts me into Vi mode. Now I've nothing against Vi
but if I wanted to use it, I have the real thing (well Vim anyway) at
the command prompt. Unfortunately on
Gary Dale, Di 05 Jul 2016 05:51:31 CEST:
> There seems to be a combination of keystrokes that I accidentally hit
> from time to time that puts me into Vi mode. Now I've nothing against Vi
> but if I wanted to use it, I have the real thing (well Vim anyway) at
> t
There seems to be a combination of keystrokes that I accidentally hit
from time to time that puts me into Vi mode. Now I've nothing against Vi
but if I wanted to use it, I have the real thing (well Vim anyway) at
the command prompt. Unfortunately once in it, I can't figure out how t
Renaud OLGIATI wrote:
> Michael Biebl wrote:
> > Were you dropped into the initramfs rescue shell?
>
> Yes, and
> root@ron: # vi /etc/fstab
> vi: error while loading shared libraries: libgpm.so.2: cannot open shared
> object file: No such file or directory
Sounds lik
On Mon, 26 Jan 2015 18:27:26 +0100
Michael Biebl wrote:
> Were you dropped into the initramfs rescue shell?
Yes, and http://www.olgiati-in-paraguay.org --
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.de
ebian
>system, the
>> > reboot failed, could not recognize the UUID of the new array.
>
>> > So I give the root password, and # vi /etc/fstab. Surprise ! I get
>vi:
>> > command not found
>
>> Which version of Debian? I have vi in Debian Wheezy (Sta
an
> > > system, the reboot failed, could not recognize the UUID of the new
> > > array.
> > >
> > > So I give the root password, and # vi /etc/fstab. Surprise ! I get vi:
> > > command not found
> >
> > Which version of Debian? I have vi in
> > So I give the root password, and # vi /etc/fstab. Surprise ! I get vi:
> > command not found
> Which version of Debian? I have vi in Debian Wheezy (Stable).
You have it in the rescue console ?
Cheers,
Ron.
--
A new koan:
On Mon, 26 Jan 2015 13:26:12 -0300
Renaud (Ron) OLGIATI wrote:
Hello Renaud,
>So I give the root password, and # vi /etc/fstab. Surprise ! I get vi:
>command not found
{snip}
>How is it that such a fundamental tool as vi is missing ?
I'd hazard a guess that it was/is on the driv
I give the root password, and # vi /etc/fstab. Surprise ! I get vi:
> command not found
Which version of Debian? I have vi in Debian Wheezy (Stable).
Surely Jessie hasn't dropped it? If it was Sid, that could just be a
temporary bug.
Lisi
--
To UNSUBSCRIBE, email to debian-user-r
As a Debian newbee, I was very surprised this week-end: on the first reboot
after adding a second raid array to my newly installed Debian system, the
reboot failed, could not recognize the UUID of the new array.
So I give the root password, and # vi /etc/fstab. Surprise ! I get vi: command
not
On 01/05/2014 03:37 AM, Osamu Aoki wrote:
> Choose 1-7 []: 6
> $ dpkg -S select-editor
> sensible-utils: /usr/bin/select-editor
> sensible-utils: /usr/share/man/man1/select-editor.1.gz
>
> As I see its changelog, it is only in testing/sid:
so, it isn't in wheezy .. that's what I figured out:)
# sel
On Thu, Jan 02, 2014 at 11:17:24AM +, Curt wrote:
> On 2014-01-02, Paul Cartwright wrote:
> > On 01/01/2014 08:01 PM, John Hasler wrote:
> >> man select-editor
> > man select-editor
> > No manual entry for select-editor
>
> I think you need to install 'sensible-utils', which provides
>
> /us
> On 01/01/2014 07:00 PM, Richard Hector wrote:
> > Also perhaps:
> >
> > aptitude purge nano :-)
> >
> > Richard
> thanks, I might do that also, since I use
uot; wrote:
> >
> > On 01/01/2014 07:00 PM, Richard Hector wrote:
> > > Also perhaps:
> > >
> > > aptitude purge nano :-)
> > >
> > > Richard
> > thanks, I might do that also, since I use either VI or gedit..
> >
>
> Yo
t; >
> > aptitude purge nano :-)
> >
> > Richard
> thanks, I might do that also, since I use either VI or
gedit..
>
You do know about gvim right?
gvim, is basically vim-tiny? portable? If I tra
On Jan 1, 2014 7:43 PM, "Paul Cartwright" wrote:
>
> On 01/01/2014 07:00 PM, Richard Hector wrote:
> > Also perhaps:
> >
> > aptitude purge nano :-)
> >
> > Richard
> thanks, I might do that also, since I use either VI or gedit..
>
You do know about gvim right?
On 2014-01-02, Paul Cartwright wrote:
> On 01/01/2014 08:01 PM, John Hasler wrote:
>> man select-editor
> man select-editor
> No manual entry for select-editor
I think you need to install 'sensible-utils', which provides
/usr/bin/sensible-browser
/usr/bin/sensible-editor
/usr/bin/sensible-pager
On 01/01/2014 08:01 PM, John Hasler wrote:
> man select-editor
man select-editor
No manual entry for select-editor
that's OK, I already did the .bashrc EDITOR=vi
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
--
To UNSUBSCRIBE, email to debian-u
man select-editor
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87d2kb9oz1@thumper.dhh.gt.org
On 01/01/2014 07:00 PM, Richard Hector wrote:
> Also perhaps:
>
> aptitude purge nano :-)
>
> Richard
thanks, I might do that also, since I use either VI or gedit..
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
--
To UNSUBSCRIBE, email to d
On 02/01/14 04:20, Markus Schönhaber wrote:
> 01.01.2014 15:09, Andreas Rönnquist:
>> On Wed, 01 Jan 2014 08:59:24 -0500,
>> Paul Cartwright wrote:
>>
>>> ok, so I have a wheezy setup. When I do a crontab -e to EDIT my
>>> crontab, it brings up a na
On 01/01/2014 10:20 AM, Markus Schönhaber wrote:
> ... and if you rather want to change the system default, do
>
> update-alternatives --config editor
>
> as root.
>
> P.S.: Sorry Andeas for the PM. Shouldn't have happened, but the brain
> controlling my fingers seems to be still stuck in 2013...
t
01.01.2014 15:09, Andreas Rönnquist:
> On Wed, 01 Jan 2014 08:59:24 -0500,
> Paul Cartwright wrote:
>
>> ok, so I have a wheezy setup. When I do a crontab -e to EDIT my
>> crontab, it brings up a nano session. I'm a VI kind guy, how do I
>> change that so VI comes
Paul Cartwright writes:
> ok, so I have a wheezy setup. When I do a crontab -e to EDIT my crontab,
> it brings up a nano session. I'm a VI kind guy, how do I change that so
> VI comes up??
Most generally, you should set the environmental variable EDITOR to be
your favorite editor
On Wed, 01 Jan 2014 08:59:24 -0500,
Paul Cartwright wrote:
>ok, so I have a wheezy setup. When I do a crontab -e to EDIT my
>crontab, it brings up a nano session. I'm a VI kind guy, how do I
>change that so VI comes up??
>
It gets the editor from the EDITOR environment variable
ok, so I have a wheezy setup. When I do a crontab -e to EDIT my crontab,
it brings up a nano session. I'm a VI kind guy, how do I change that so
VI comes up??
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
--
To UNSUBSCRIBE, email to debian-user
This took me too long to figure it out but in case anybody else was
wondering how to do this.
This is the correct line...
bind -m vi-insert '"\e.": yank-last-arg'
On Sat, Jun 9, 2012 at 8:36 PM, alberto fuentes wrote:
> I set it to emacs
> set -o emacs
>
I set it to emacs
set -o emacs
then i saw the function i was looking for was yank-last-arg
"\e.": yank-last-arg
"\e_": yank-last-arg
I tried to create it for vi mode with
set -o vi
bind -m vi-insert "\e.": yank-last-arg
but it does not work... as
that nano's called by visudo (paradoxically)
>>> is that visudo calls "/usr/bin/editor" and the alternatives system
>>> maps it to "/usr/bin/nano".
>>>
>>> You can run visudo with "EDITOR=vi visudo" if you just want vi in this
>
On 03/20/2011 10:15 PM, Tom H wrote:
On Sun, Mar 20, 2011 at 8:30 PM, Joel Rees wrote:
It's nano and the reason that nano's called by visudo (paradoxically)
is that visudo calls "/usr/bin/editor" and the alternatives system
maps it to "/usr/bin/nano".
You can run
On Sun, Mar 20, 2011 at 8:30 PM, Joel Rees wrote:
It's nano and the reason that nano's called by visudo (paradoxically)
is that visudo calls "/usr/bin/editor" and the alternatives system
maps it to "/usr/bin/nano".
You can run visudo with "EDITOR=vi visudo&qu
(Still forgetting and hitting the reply button instead of reply-all
followed by manually clearing the to: field.
Sorry, Rob.)
-- Forwarded message --
From: Joel Rees
Date: Mon, Mar 21, 2011 at 9:20 AM
Subject: Re: [help-a-newb] adduser okay? (problem with authenticating
with gui
> > I don't want the editor to do whatever special screen buffer
> > swapping, or whatever it is, that prevents me from scrolling back in
> > my terminal history when the editor is open, and then clears away
> > the screen and redisplays what was there before after the editor is
> > closed.
>
> Thi
On Tue, Nov 4, 2008 at 6:36 AM, Cameron Hutchison <[EMAIL PROTECTED]> wrote:
> Sven Joachim <[EMAIL PROTECTED]> writes:
>
>>On 2008-11-04 06:28 +0100, Matt Miller wrote:
>
> Also, I don't want the editor to do whatever special screen buffer
> swapping, or whatever it is, that prevents me
Sven Joachim <[EMAIL PROTECTED]> writes:
>On 2008-11-04 06:28 +0100, Matt Miller wrote:
>>> > Also, I don't want the editor to do whatever special screen buffer
>>> > swapping, or whatever it is, that prevents me from scrolling back in
>>> > my terminal history when the editor is open, and then c
On 2008-11-04 06:28 +0100, Matt Miller wrote:
>> > Also, I don't want the editor to do whatever special screen buffer
>> > swapping, or whatever it is, that prevents me from scrolling back in
>> > my terminal history when the editor is open, and then clears away
>> > the screen and redisplays what
> > From GNOME terminal, when I:
> >
> > vi x :set nu
> >
> > the line numbers are colored, and I want to get rid of that.
>
> you could change the default alternative setup to point to nvi
> instead.
Thanks, that got rid of the colorized line numbers.
On Sat, 2008-11-01 at 23:16 +0100, Matt Miller wrote:
> >From GNOME terminal, when I:
>
> vi x
> :set nu
>
> the line numbers are colored, and I want to get rid of that. Also, I
> don't want the editor to do whatever special screen buffer swapping, or
> whate
>From GNOME terminal, when I:
vi x
:set nu
the line numbers are colored, and I want to get rid of that. Also, I
don't want the editor to do whatever special screen buffer swapping, or
whatever it is, that prevents me from scrolling back in my terminal
history when the editor is open,
[EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>
> Vim really is Improved.
I agree. However, that can be a feature or a detriment, depending on
the situation. Don't expect vim features in all instances where you'd
expect vi to fill the bill. Bare metal commercial Unix comes to
[This message has also been posted to linux.debian.user.]
In article <[EMAIL PROTECTED]>, David Fox wrote:
> On 11/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>> I tried to use the equivs package to inform Etch that my
>> custom vim "provides vi",
Joseph L. Casale <[EMAIL PROTECTED]> wrote:
> While you are at it, consider using vim instead of vi unless you have a good
> reason not to do so.
this statement leads naturally into the next:
> Well, therein lies my lack of experience! I didn't even know there was a
> di
On 11/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I tried to use the equivs package to inform Etch that my
> custom vim "provides vi", and link it to the
> /etc/alternatives/vi, but I got lost in the complexity of it.
I am not so sure that you need to go
[This message has also been posted to linux.debian.user.]
[use vim, not [n]vi]
In article <[EMAIL PROTECTED]>, Joseph L. Casale wrote:
>
> Well, therein lies my lack of experience! I didn't even know there
>was a difference, vim is what I "meant" to use but didn&#
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Kamaraju S Kusumanchi
Sent: Thursday, November 29, 2007 10:01 PM
To: debian-user@lists.debian.org
Subject: Re: vi issue in etch
Joseph L. Casale wrote:
> Hi everyone,
> I have my keyboard setup as us and in the c
Joseph L. Casale wrote:
> Hi everyone,
> I have my keyboard setup as us and in the console every key works
> correctly. In vi though everything is messed up! The standard shortcuts
> don't work. While following a tutorial, after an apt-get of a series of
> apps I noticed it s
Hi everyone,
I have my keyboard setup as us and in the console every key works correctly. In
vi though everything is messed up! The standard shortcuts don't work. While
following a tutorial, after an apt-get of a series of apps I noticed it start
working like it should?
Is there some
On Mon, Mar 19, 2007 at 09:45:31PM -0400, Joey Hess wrote:
> Paul E Condon wrote:
> > 'vi' is not in this list, so I can't say what vim.tiny should do when
> > it is invoked via the update-alternatives symlink, vi, but I think it
> > is not doing something th
Paul E Condon wrote:
> 'vi' is not in this list, so I can't say what vim.tiny should do when
> it is invoked via the update-alternatives symlink, vi, but I think it
> is not doing something that its maintainers intend. Is this a bug? Or
> is it working in some mode
On Monday 19 March 2007 22:22, Paul E Condon wrote:
> Now, I think I have never actually used vi. Instead, I have always been
> using versions of vim that were loaded when I typed 'vi'. My ignorance is
> revealed, but I learn, slowly.
The closest free piece of software you can
On Mon, Mar 19, 2007 at 05:02:09PM -0400, Kamaraju S Kusumanchi wrote:
> Paul E Condon wrote:
>
>
> > When I was using Sarge, and early upgrades to Etch, I had avoided
> > using vim because I never felt I had the time to learn about its
> > 'improved features
Paul E Condon wrote:
> When I was using Sarge, and early upgrades to Etch, I had avoided
> using vim because I never felt I had the time to learn about its
> 'improved features'. Now, when I run vi, it behaves in a strange
> way that I dislike, and I can get back to
On 03/19/07 15:32, Paul E Condon wrote:
> I have done a new install of etch, and discovered a situation
> that I find problematic. I don't know vi or vim well enough to
> recognize which I am actually running by observing the behavior
> of the running program, so some of my d
I have done a new install of etch, and discovered a situation
that I find problematic. I don't know vi or vim well enough to
recognize which I am actually running by observing the behavior
of the running program, so some of my description of the situation
should be discounted if known to be u
Bill Warren wrote:
>
>
>
> -Original Message-
> From: Angelo Bertolli [mailto:[EMAIL PROTECTED]
> Sent: Mon 12/18/2006 10:20 PM
> To: Bill Warren
> Cc: debian-user@lists.debian.org
> Subject: Re: Problems with phpbb and mysql vi dselect
>
> Bill Warren wro
Angelo Bertolli wrote:
>Bill Warren wrote:
>
>
>>
>>-Original Message-
>>From: Angelo Bertolli [mailto:[EMAIL PROTECTED]
>>Sent: Mon 12/18/2006 10:20 PM
>>To: Bill Warren
>>Cc: debian-user@lists.debian.org
>>Subject: Re: Problems wit
-Original Message-
From: Angelo Bertolli [mailto:[EMAIL PROTECTED]
Sent: Mon 12/18/2006 10:20 PM
To: Bill Warren
Cc: debian-user@lists.debian.org
Subject: Re: Problems with phpbb and mysql vi dselect
Bill Warren wrote:
>
> Hello,
>
> I have dselected phpbb2 and mysql. The
Bill Warren wrote:
>
> Hello,
>
> I have dselected phpbb2 and mysql. The database is done and works.
> When I go to http://mywebsite.com/phpbb the web page I get:
>
> The database module for the database you are using, MySQL, is not
> available. Please (re)install the php4-mysql package or if it's
Hello,
I have dselected phpbb2 and mysql. The database is done and works. When I go to
http://mywebsite.com/phpbb the web page I get:
The database module for the database you are using, MySQL, is not available.
Please (re)install the php4-mysql package or if it's already installed, add
extensi
MA LA TOGLIETE STA ROBA VECCHIA DI 10 ANNI???
Grazie
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
You should know that Vim behaves differently when invoked as vi then
when invoked as vim. Therefore, you may want to use vim from now on.
or use elvis. i have come to like elvis quite a lot. the debian install
defaults to the elvis GUI, which i can take or leave, but i'm sure there
* David Baron <[EMAIL PROTECTED]> [2006-05-24 16:15]:
> In more recent versions of vi (vim), the insert/replace keyed
> functionality is no longer working as it was. The prompt "insert" or
> "replace" does not appear, one cannot go to the very end (after las
On Wed, May 24, 2006 at 05:15:19PM +0300, David Baron wrote:
> In more recent versions of vi (vim), the insert/replace keyed
> functionality is no longer working as it was. The prompt "insert" or
> "replace" does not appear, one cannot go to the very end (after last
On 24/05/06, David Baron <[EMAIL PROTECTED]> wrote:
In more recent versions of vi (vim), the insert/replace keyed functionality is
no longer working as it was. The prompt "insert" or "replace" does not
appear, one cannot go to the very end (after last character) of t
In more recent versions of vi (vim), the insert/replace keyed functionality is
no longer working as it was. The prompt "insert" or "replace" does not
appear, one cannot go to the very end (after last character) of the line, and
the direction keys give (escaped) characters in
Hello!
When I "su" to root and start "vi", a bunch of these messages appear:
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Xlib: connection to ":0.0" refused by server
Chris Howie explained:
> vim tries to connect X for access to the X clipboard.
>
> :help x11-
Hello!
When I "su" to root and start "vi", a bunch of these messages appear:
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Xlib: connection to ":0.0" refused by server
Chris Howie explained:
vim tries to connect X for access to the X clipboard.
:help x11-selection
I th
On Sat, Feb 18, 2006 at 09:09:35PM -0800, Rob Blomquist wrote:
> Is there anyway to fix this problem? It drives me nuts. Basically the gui
> flashes occassionally and seems to miss commands I give it.
Could this be the visual bell? I have encountered this in sarge,
although it (the regular beep)
Is there anyway to fix this problem? It drives me nuts. Basically the gui
flashes occassionally and seems to miss commands I give it.
Rob
--
Mountlake Terrace, WA, USA
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Monday 06 February 2006 03:20 am, Karsten M. Self wrote:
> You've apparently got the gvim variant of vim installed, and it may be
> doing stupid things presuming it's got an X display active.
>
> Try:
>
>unset DISPLAY
>vi foo
>
> ... and see if th
Kumar Appaiah wrote:
> I think vim is trying to change the title of the Konsole window to
> Vim.
Setting the title is done through escape codes, not X:
echo -e '\033]2;Hello, World!\a'
--
Chris Howie
http://www.chrishowie.com
-BEGIN GEEK CODE BLOCK-
Version: 3.1
GCS/IT d-(--) s:- a--->
On Mon, Feb 06, 2006 at 01:20:04AM -0800, Karsten M. Self wrote:
> > Xlib: connection to ":0.0" refused by server
> > Xlib: No protocol specified
> >
> > Xlib: connection to ":0.0" refused by server
> > Xlib: No protocol specified
> >
> > Xlib: connection to ":0.0" refused by server
> > Xlib: No
Karsten M. Self wrote:
> You've apparently got the gvim variant of vim installed, and it may be
> doing stupid things presuming it's got an X display active.
vim tries to connect X for access to the X clipboard.
:help x11-selection
--
Chris Howie
http://www.chrishowie.com
-BEGIN GEEK CODE
on Sun, Feb 05, 2006 at 05:08:15PM -0600, Anthony Simonelli ([EMAIL PROTECTED])
wrote:
> Hi there. I'm tried to get used to vi as an editor since it is found on
> nearly every Unix and Unix-like system and I've heard that those who are
> proficient at it are able to edi
PROTECTED]> wrote:
> > > > I'm running KDE and use Konsole but everytime I invoke vi from
> > > > Konsole, I get the following:
> > > >
> > > > Xlib: connection to ":0.0" refused by server
> > > > Xlib: No protocol spe
On Sunday 05 February 2006 08:50 pm, Duncan Anderson wrote:
> On Monday, 6 February 2006 04:19, Shawn Lamson wrote:
> > On Sun, 05 Feb 2006 17:08:15 -0600
> >
> > Anthony Simonelli <[EMAIL PROTECTED]> wrote:
> > > I'm running KDE and use Konsole but everyt
On Monday, 6 February 2006 04:19, Shawn Lamson wrote:
> On Sun, 05 Feb 2006 17:08:15 -0600
>
> Anthony Simonelli <[EMAIL PROTECTED]> wrote:
> > I'm running KDE and use Konsole but everytime I invoke vi from Konsole, I
> > get the following:
> >
> >
On Sun, 05 Feb 2006 17:08:15 -0600
Anthony Simonelli <[EMAIL PROTECTED]> wrote:
> I'm running KDE and use Konsole but everytime I invoke vi from Konsole, I get
> the following:
>
> Xlib: connection to ":0.0" refused by server
> Xlib: No protocol specified
ha
Hi there. I'm tried to get used to vi as an editor since it is found on
nearly every Unix and Unix-like system and I've heard that those who are
proficient at it are able to edit files faster than using any other editor.
I'm running KDE and use Konsole but everytime I invoke vi
When I use escape-slash to search my history in bash vi mode I get wierd
results. For example typing this:
[EMAIL PROTECTED] /ssh
then hitting , gets me this:
[EMAIL PROTECTED] t
mjssh -oServerAliveInterval=90 [EMAIL PROTECTED]
Or this:
[EMAIL PROTECTED] al=90 [EMAIL PROTECTED]
I have no
On Sunday 01 January 2006 08:20 pm, Rogério Brito wrote:
> On Jan 01 2006, Mitchell Laks wrote:
> > How to dispense with it?
>
> Do you possibly have anything like ecb, semantic, eieio, speedbar-*,
> cedet-* installed in your machine? If you don't have any use for them,
> I'd suggest you to uninst
On Jan 01 2006, Mitchell Laks wrote:
> ede-speedbar semantic-idle
>
> flash by in the minibuffer. What in the world is that?
Those are packages packages for development of large programs. You can
learn more if you search google for cedet or ecb.
> How to dispense with it?
Do you possibly have a
OOps: The problem was that emacs was doing a reverse dns lookup or something.
The clue was "10 seconds".
As soon as I put the hostname and ip in /etc/hosts emacs went back to
immediate.
I have never been able to configure a local caching dns server on debian with
bind. I dont know how, desp
1 - 100 of 583 matches
Mail list logo
