June 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Anybody using pcl-cvs 1.46 with any success? 25 years, 1 month

Adrian Aichner

>>>>> "Paul" == Paul Krause <pkrause(a)ibelong.com> writes: Paul> This is a multi-part message in MIME format. Paul> ------=_NextPart_000_0048_01BFCBDD.ACE457C0 Paul> Content-Type: text/plain; Paul> charset="iso-8859-1" Paul> Content-Transfer-Encoding: 7bit Paul> Charles G Waldman writes: >> Adrian Aichner writes: >>> >>> Today I found that commiting files does not work. >>> >>> the argument to -m does not get quoted at all. How is this supposed >>> to work at all? >> >> I haven't seen this behavior here! I've been merrily committing files >> and the CVS logs look normal... hmmm Paul> I have. I had to hack vc-backend-checkin to make it work. Hi Paul, you seem to commit via vc, AFAICS. I just tried this using vc 1.23 and it worked fine. Paul> A patch is attached, but somehow I don't think this is the Paul> right fix. -- Paul Krause 781.672.8220 fax 781.466.9821 Paul> iBelong Inc, 950 Winter St, Waltham MA 02125 What version of vc do you use? Best regards, Adrian

4 participants
4 comments

toolbar enabled-p slot broken... 25 years, 1 month

William M. Perry

Unless I'm misunderstanding the documentation. It seems that the ENABLED-P slot in the button descriptor only gets evaluated when the specifier is evaluated. I am in the midst of writing all the test cases for XEmacs/GTK and first off was making sure dynamically-enabled toolbar buttons worked. Guess what, they don't work in XEmacs 21.1.10 either. :( With this test function: ------------------------------------------------------------------------------- (defvar gtk-torture-test-toolbar-open-active-p t) (defvar gtk-torture-test-toolbar '([toolbar-file-icon (lambda () (setq gtk-torture-test-toolbar-open-active-p (not gtk-torture-test-toolbar-open-active-p))) gtk-torture-test-toolbar-open-active-p "Open a file"] [toolbar-folder-icon toolbar-dired t "Edit a directory"] [toolbar-disk-icon toolbar-save t "Save buffer"] [toolbar-printer-icon toolbar-print t "Print buffer"] [toolbar-cut-icon toolbar-cut t "Kill region"] [toolbar-copy-icon toolbar-copy t "Copy region"] [toolbar-paste-icon toolbar-paste t "Paste from clipboard"] [toolbar-undo-icon toolbar-undo t "Undo edit"] [toolbar-spell-icon toolbar-ispell t "Check spelling"] [toolbar-replace-icon toolbar-replace t "Search & Replace"] [toolbar-mail-icon toolbar-mail t "Read mail"] [toolbar-info-icon toolbar-info t "Info documentation"] [toolbar-compile-icon toolbar-compile t "Start a compilation"] [toolbar-debug-icon toolbar-debug t "Start a debugger"] [toolbar-news-icon toolbar-news t "Read news"] )) (defun gtk-torture-test-toolbar () (interactive) (switch-to-buffer (get-buffer-create "Toolbar testing")) (set-specifier default-toolbar gtk-torture-test-toolbar (current-buffer)) (set-specifier default-toolbar-visible-p t (current-buffer))) ------------------------------------------------------------------------------- If you do M-x gtk-torture-test-toolbar, you will get a buffer with a toolbar that looks normal, but if you click the 'open' button, I would have expected the toolbar button to be immediately marked as disabled. But it is not until you switch buffers to another buffer and then back to the 'Toolbar testing' buffer. If this is the way things are meant to be, then the documentation in default-toolbar needs to be updated to reflect this. It makes it sound like this slot will get evaluated quite a bit. Perhaps if there was a (set-toolbar-dirty-flag position) function... but that is kind of ugly. -Bill P.

1 participants
0 comments

Re: Anders Lindgren's autorevert and follow packages 25 years, 1 month

Gerd Boerrigter

Charles G Waldman <cgw(a)fnal.gov> writes: > I'd like to make the required fixes so that follow-mode and > auto-revert-mode work correctly under XEmacs, and then add these > packages to the XEmacs package tree. Two questions: Just out of curiosity, what is the problem with auto-revert-mode? I am using it for quite a while now (with XEmacs 21.1.7) and could not see a problem. And of course, I would be happy if those modes would be part of XEmacs. Gerd

1 participants
0 comments

Anders Lindgren's autorevert and follow packages 25 years, 1 month

Charles G Waldman

Anders Lindgren's Emacs page [1] has some nice Elisp hacks, unfortunately several of them do not work correctly with XEmacs. There have been some patches floating around in the mailing list for some of the problems. I'd like to make the required fixes so that follow-mode and auto-revert-mode work correctly under XEmacs, and then add these packages to the XEmacs package tree. Two questions: A) Any objections to doing so? B) Where should they be added? I'm thinking of oa/text-modes Footnotes: [1] http://www.csd.uu.se/~andersl/emacs.shtml

1 participants
0 comments

Anybody using pcl-cvs 1.46 with any success? 25 years, 1 month

Adrian Aichner

Hello Michael, hello All! I coming to the conclusion more and more that the new port of ftp://rum.cs.yale.edu/pub/monnier/pcl-cvs/pcl-cvs-2.9.9.tar.gz isn't really working in XEmacs, if at all. Has anybody commited a file with this pcl-cvs-version "v2_9_9" ? I have reported the ring-insert problem a few days back. Today I found that commiting files does not work. the argument to -m does not get quoted at all. How is this supposed to work at all? eg. cvs commit -m this ain't gonna work will-it.txt I just checked that our previous pcl-cvs 1.41 does quote its arguments before executing the command. Best regards, Adrian

4 participants
3 comments

Re: Anybody using pcl-cvs 1.46 with any success? 25 years, 1 month

Adrian Aichner

>>>>> "Charles" == Charles G Waldman <cgw(a)fnal.gov> writes: Charles> Adrian Aichner writes: >> >> I coming to the conclusion more and more that the new port of >> ftp://rum.cs.yale.edu/pub/monnier/pcl-cvs/pcl-cvs-2.9.9.tar.gz >> isn't really working in XEmacs, if at all. Charles> There are definitely problems with it - see e.g. my Charles> posting Charles> http://www.xemacs.org/list-archives/xemacs-beta/200005/msg00416.html Charles> concerning the reference to the missing function Charles> `vc-resolve-conflicts' Ah, yes, I saw that. Charles> but, despite this I am using it on a daily basis without Charles> *too* much grief. Hmmh ... Can you commit from the *cvs* buffer useing c runs the command cvs-mode-commit ? >> Has anybody commited a file with this >> pcl-cvs-version "v2_9_9" Charles> Yes. >> >> Today I found that commiting files does not work. >> >> the argument to -m does not get quoted at all. How is this supposed >> to work at all? Charles> I haven't seen this behavior here! I've been merrily Charles> committing files and the CVS logs look normal... hmmm Using c runs the command cvs-mode-commit with multi-word commit messages with whitespace between the words? I am baffled. Adrian Charles> I have "v2_9_9" of pcl-cvs - I wonder what the difference Charles> is? I built mine from source from the xemacs-packages Charles> CVS tree, did you build from source or download the Charles> binary package? I installed the binary package 1.46. The latest CVS sources don't show any quoting of the commit message either. Best regards, Adrian

1 participants
0 comments

Re: 21.2.34 crash 25 years, 1 month

Raymond Toy

>>>>> "Andy" == Andy Piper <andy(a)xemacs.org> writes: Andy> Attached Thank you! It applied just fine and works just fine. It even takes care of the crash I was getting in loading up eudc-export that I previously reported about. It kind of went away in 21.2.33, came back with a vengeance in 21.2.34, but with this patch, I don't see it anymore, and it is 100% repeatable in 21.2.34. Cool! Ray

1 participants
0 comments

Re: 21.2.34 crash 25 years, 1 month

Nick V. Pakoulin

Andy Piper <andy(a)xemacs.org> writes: > [1 <text/plain; us-ascii (7bit)>] > At 12:34 PM 5/31/00 -0400, Raymond Toy wrote: > >If you have the time, can you point out which patch fixes this? I > >can't access the CVS sources, and I'm getting this crash every hour or > >two depending on how often I read my mail and news with XEmacs. This > >makes it unusable for me. > > Attached > > andy > [2 hash.patch <text/plain; iso-8859-1 (quoted-printable)>] > Index: src/elhash.c > =================================================================== > RCS file: /usr/CVSroot/XEmacs/xemacs/src/elhash.c,v > retrieving revision 1.14.2.23 > diff -u -r1.14.2.23 elhash.c Great! It works (keeping fingers crossed ;) ) Nick. > -------------------------------------------------------------- > Dr Andy Piper > Principal Consultant, BEA Systems Ltd

1 participants
0 comments

Re: --srcdir and running-in-place 25 years, 1 month

Michael Sperber

>>>>> "Stephen" == Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: Stephen> (2) building with --srcdir=/coda/XEmacs/21.1, running src/xemacs Stephen> from the build directory or /tmp/XEmacs/Builds/21.1/src/xemacs Stephen> from /coda/XEmacs/21.1 gives Stephen> bash-2.04$ /tmp/XEmacs/Builds/21.1/src/xemacs Stephen> WARNING: Stephen> Couldn't find obvious defaults for: Stephen> doc-directory Stephen> exec-directory Stephen> lisp-directory Stephen> Perhaps some directories don't exist, or the XEmacs executable, Stephen> /tmp/XEmacs/Builds/21.1/src/xemacs Stephen> is in a strange place? I always build like that, and have never had any problems. (Obviously---I wrote the code in question :-} ) Can you run with -debug-paths and post the output? -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

2 participants
1 comments

--srcdir and running-in-place 25 years, 1 month

Stephen J. Turnbull

I was building XEmacs in the source directory on several different machines, but discovered that I was not keeping the directories consistent. So I moved the sources to a network file system (Coda), and started using --srcdir. I have discovered that (1) building in the source tree, I can run src/xemacs without trouble (2) building with --srcdir=/coda/XEmacs/21.1, running src/xemacs from the build directory or /tmp/XEmacs/Builds/21.1/src/xemacs from /coda/XEmacs/21.1 gives bash-2.04$ /tmp/XEmacs/Builds/21.1/src/xemacs WARNING: Couldn't find obvious defaults for: doc-directory exec-directory lisp-directory Perhaps some directories don't exist, or the XEmacs executable, /tmp/XEmacs/Builds/21.1/src/xemacs is in a strange place? (3) building with --srcdir=/coda/XEmacs/21.1, doing make install, and then running-in-place works fine, either cwd This is bad, obviously. It's going to cause hard to diagnose problems with docstring skew a lot, and similar problems with other stuff from those directories more rarely I would suppose. I guess this is related to Martin's plaint about "can't move hierarchies," but at least to me this --srcdir problem was not an obvious consequence of Martin's observation. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

1 participants
0 comments

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta June 2000