Update of /services/emacs-rcp/cvsroot/rcp/lisp
In directory lucy:/export/home/grossjoh/work/emacs-rcp/rcp/lisp
Modified Files:
rcp.el
Log Message:
Change CVS instructions, include new todo item.
Update of /services/emacs-rcp/cvsroot/rcp/lisp
In directory bonny:/tmp/cvs-serv15704
Added Files:
rcp-vc.el
Log Message:
Moved the VC integration code into a separate file.
Update of /services/emacs-rcp/cvsroot/rcp/lisp
In directory lucy:/export/home/grossjoh/work/emacs-rcp/rcp/lisp
Modified Files:
rcp.el
Log Message:
rcp-handle-file-newer-than-file-p: (signal 'file-error ...) rather
than (error ...)
Pete Forman [EMAIL PROTECTED] writes:
I thought we were trying to cut down on traffic. Wouldn't something
like "echo foo; echo bar" be adequate.
The idea is that `ls -l /' will produce date values in the local
format of the remote host. `echo foo; echo bar' just produces ascii
characters.
On Fri, 26 May 2000, Kai Großjohann [EMAIL PROTECTED]
wrote:
"Daniel Pittman" [EMAIL PROTECTED] writes:
On Fri, 26 May 2000, Kai Großjohann
[EMAIL PROTECTED] wrote:
I think that if you signal a continuable error, that would be best.
At least it's semi-obvious that something went wrong
On Fri, 26 May 2000, Pete Forman [EMAIL PROTECTED]
wrote:
Kai Großjohann writes:
Pete Forman [EMAIL PROTECTED] writes:
I thought we were trying to cut down on traffic. Wouldn't
something like "echo foo; echo bar" be adequate.
The idea is that `ls -l /' will produce date
On Fri, 26 May 2000, Kai Großjohann [EMAIL PROTECTED]
wrote:
"Daniel Pittman" [EMAIL PROTECTED] writes:
On Fri, 26 May 2000, Kai Großjohann
[EMAIL PROTECTED] wrote:
Well, I've got to read up on continuable errors, then. Is
`file-error' a continuable error?
Hmmm. Yes, in a quick
On Fri, 26 May 2000, Kai Großjohann [EMAIL PROTECTED]
wrote:
Pete Forman [EMAIL PROTECTED] writes:
Again I'm unsure as to whether you're looking for date or EOL
conventions. I don't use MULE.
I wish I was sure. I think I'm confused by the whole thing. I know
that we need to grok EOL
Do you think it would make sense to have a look at /etc/motd? That
could shed some light on the coding used. Though I'm not sure if
there are places where the coding for file _names_ is normally
different from the coding for file _contents_.
Maybe Yuji has some information on this?
kai
--
I
On Fri, 26 May 2000, Kai Großjohann [EMAIL PROTECTED]
wrote:
Do you think it would make sense to have a look at /etc/motd? That
could shed some light on the coding used. Though I'm not sure if
there are places where the coding for file _names_ is normally
different from the coding for file
[EMAIL PROTECTED] (Kai Großjohann) writes:
Maybe Yuji has some information on this?
Oops, I think that should have been Yamano-san.
kai
--
I like BOTH kinds of music.
[EMAIL PROTECTED] writes:
This would be a wonderful thing to do. Thanks, Yamano-san (I hope I
got that right).
You are right, my family name is Yamano.
Maybe Yuji has some information on this?
Oops, I think that should have been Yamano-san.
Don't worry, please call me Yuji.
Do you
[EMAIL PROTECTED] writes:
Do you think it would make sense to have a look at /etc/motd? That
could shed some light on the coding used.
Please let me know why /etc/motd?
I don't understand this issue, maybe.
On my NetBSD box,
- /etc/motd doesn't contain Japanese character.
- NetBSD doesn't
On Sat, 27 May 2000, Yuji Yamano [EMAIL PROTECTED] wrote:
[...]
Thanks.
Could you add rcsid ($Id$) to rcp.texi? I believe it is useful to sync
the Japanese version with the English one.
It's done already. :)
Daniel
--
Bad science and bad religion simply swap roles,
the former
Update of /services/emacs-rcp/cvsroot/rcp/lisp
In directory bonny:/tmp/cvs-serv18288
Modified Files:
rcp.el
Log Message:
XEmacs compatibility fix: `detect-coding-region' takes a buffer as the third
argument in XEmacs. So, we get a list of coding systems and take the first
one.
15 matches
Mail list logo
