Re: commit problem with cvs mode

Re: commit problem with cvs mode

[Sam Halliday]

Arnaud Vandyck wrote:
> I think I'am having some troubles with  the commit in cvs mode. I have
> a project on sourceforge and it  takes times and times to commit
> ("waiting process to die" I think) but when I do it in a console, it's
> rather fast and ok!? 

i know for savannah commits, you need this in your ~/.emacs

  (setenv "CVS_RSH" "ssh")

to use ssh login (i think sourceforge is the same). maybe you forgot to
do this and cvs is trying to use rsh instead of ssh; but then again, i
would really expect cvs to moan if that was the case. try that setenv
anyway.

can you tell us about any relevant parts of your ~/.emacs file?

Re: commit problem with cvs mode

[Kai Großjohann]

Arnaud Vandyck <arnaud.vandyck@ulg.ac.be> writes:

> I think I'am having some troubles with  the commit in cvs mode. I have a
> project on sourceforge and it  takes times and times to commit ("waiting
> process to die" I think) but when I do it in a console, it's rather fast
> and ok!? 

PCL-CVS doesn't provide error messages by default.  But when you hit
C-c C-c to interrupt the cvs subprocess, then you usually find some
message in the *cvs* buffer.

What do you see?  Does the message tell you what's wrong?
-- 
This line is not blank.

Re: commit problem with cvs mode

[Arnaud Vandyck]

Sam Halliday <devnull@example.com> wrote:
> (setenv "CVS_RSH" "ssh")

That solves my problem! many thanks ;)

-- Arnaud Vandyck, STE fi, ULg
   Formateur Cellule Programmation.

Re: commit problem with cvs mode

[Arnaud Vandyck]

kai.grossjohann@gmx.net (Kai Großjohann) wrote:
> Arnaud Vandyck <arnaud.vandyck@ulg.ac.be> writes:
> 
> > I think  I'am having some  troubles with the  commit in cvs  mode. I
> > have a project on sourceforge and it takes times and times to commit
> > ("waiting process  to die" I think) but  when I do it  in a console,
> > it's rather fast and ok!?
> 
> PCL-CVS doesn't provide  error messages by default.  But  when you hit
> C-c C-c  to interrupt the cvs  subprocess, then you  usually find some
> message in the *cvs* buffer.
> 
> What do you see?  Does the message tell you what's wrong?

Problem solved with Sam's mail, many thanks to both of you :)

-- Arnaud Vandyck, STE fi, ULg
   Formateur Cellule Programmation.

Re: commit problem with cvs mode

[Artur Hefczyc]

Sam Halliday wrote:

> Arnaud Vandyck wrote:
>> I think I'am having some troubles with  the commit in cvs mode. I have
>> a project on sourceforge and it  takes times and times to commit
>> ("waiting process to die" I think) but when I do it in a console, it's
>> rather fast and ok!?
> i know for savannah commits, you need this in your ~/.emacs
>   (setenv "CVS_RSH" "ssh")
It is good to set this variable on shell level so it can be used
not only yb emacs (and pcl-cvs) but also by command line
or other cvs clients.

for example for bash shell add to your .bashrc following

export CVS_RSH=ssh

Artur
-- 
Artur Hefczyc
Open Source Developer
http://www.geotools.org/
http://wttools.sourceforge.net/

Re: commit problem with cvs mode

[Sam Halliday]

Artur Hefczyc wrote:
> Sam Halliday wrote:
> > Arnaud Vandyck wrote:
> >> I think I'am having some troubles with  the commit in cvs mode. I
> >have> a project on sourceforge and it  takes times and times to
> >commit> ("waiting process to die" I think) but when I do it in a
> >console, it's> rather fast and ok!?
> > i know for savannah commits, you need this in your ~/.emacs
> >   (setenv "CVS_RSH" "ssh")
> It is good to set this variable on shell level so it can be used
> not only yb emacs (and pcl-cvs) but also by command line
> or other cvs clients.
> 
> for example for bash shell add to your .bashrc following
> 
> export CVS_RSH=ssh

in conjunction with setting it in ~/.emacs of course. my emacs is
spawned from within a blackbox menu, and it doesnt pick up shell
variables. thats probably what happened with Arnaud as well, because cvs
commits seemed to work from the command line.

Re: commit problem with cvs mode

[Stefan Monnier]

> in conjunction with setting it in ~/.emacs of course. my emacs is
> spawned from within a blackbox menu, and it doesnt pick up shell
> variables. thats probably what happened with Arnaud as well, because cvs
> commits seemed to work from the command line.

Please report such brain dead setups to whoever is responsible (probably
something like RedHat, Debian, ...).  There should be one place where
you can set all your envvars and have them inherited everywhere.
This place is typically ~/.bash_login or ~/.login but could be something
else.  ~/.bashrc is obviously wrong, although it might work.


        Stefan

Re: commit problem with cvs mode

[Reiner Steib]

On Tue, Jun 17 2003, Stefan Monnier wrote:

> There should be one place where you can set all your envvars and
> have them inherited everywhere.  This place is typically
> ~/.bash_login or ~/.login but could be something else.

I'd use `~/.profile' instead of `~/.bash_login'.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/

Re: commit problem with cvs mode

[Artur Hefczyc]

Stefan Monnier wrote:

>> in conjunction with setting it in ~/.emacs of course. my emacs is
>> spawned from within a blackbox menu, and it doesnt pick up shell
>> variables. thats probably what happened with Arnaud as well, because cvs
>> commits seemed to work from the command line.
> 
> Please report such brain dead setups to whoever is responsible (probably
> something like RedHat, Debian, ...).  There should be one place where
> you can set all your envvars and have them inherited everywhere.
> This place is typically ~/.bash_login or ~/.login but could be something
> else.  ~/.bashrc is obviously wrong, although it might work.
Oh, yes you are right.

At the moment I don't use RH so I can't check it to ensure however
as I remember or many boxes ".bash_profile" is read after login.
So maybe the best place is to put this variables in this file.
Or maybe on some linux distributions this is ".profile" file.

Check this, I am sure one of above should work with window managers.

Artur
-- 
Artur Hefczyc
Open Source Developer
http://www.geotools.org/
http://wttools.sourceforge.net/

Re: commit problem with cvs mode

[Sam Halliday]

Stefan Monnier wrote:
> > in conjunction with setting it in ~/.emacs of course. my emacs is
> > spawned from within a blackbox menu, and it doesnt pick up shell
> > variables. thats probably what happened with Arnaud as well, because
> > cvs commits seemed to work from the command line.
> Please report such brain dead setups to whoever is responsible

the fault is mine in this case i am afraid and not debians... i hadn't
set my window manager to load under a --login shell. silly brain dead
me... however, having emacs set this variable is more important to me
than in the shell, since i only ever use cvs from within emacs and i
have logins on several machines, all with a syncronised ~/.emacs file,
but i dont bother syncronising my .profiles.

Remap the underlying keyboard definitions

[K T Ligesh]

On Tue, Jun 17, 2003 at 09:52:17PM +0200, Reiner Steib wrote:
>      On Tue, Jun 17 2003, Stefan Monnier wrote:

 Greetings,

 I am facing a peculiar problem...

 In my viper, <C-c> is mapped to switch from insert to vi mode...

 BUt <C-c> is the prefix key for all the major-modes... SO there is a deadlock..


 I want to redifine <C-d> to generate <C-c>; WHen I press <C-d>, -everyone- will get <C-c>.

 A simple define-keying would mean that I have to remapp the hord of the different modules... This way, I can make <C-d>.

 I guess, I have to go one step below define-key..

 And help would be greatly appreciated...

 Thanks in advance..

--
:: Ligesh :: http://ligesh.com :: http://lxlabs.com :: 

Re: Remap the underlying keyboard definitions

[K T Ligesh]

On Wed, Jun 18, 2003 at 07:25:59AM +0530, K T Ligesh wrote:
>      On Tue, Jun 17, 2003 at 09:52:17PM +0200, Reiner Steib wrote:
>      >      On Tue, Jun 17 2003, Stefan Monnier wrote:
>      
>       Greetings,
>      

 Hi, I got the answer from another of the messages in the list..

 Keyboard-translation-maps..

 Yeah, Emacs is pretty neat..

 Thanks..

--
:: Ligesh :: http://ligesh.com :: http://lxlabs.com ::