December 2001 - XEmacs-Beta - XEmacs Mailing List Archives

Can't compile XEmacs 21.4.6 under cygwin 22 years, 3 months

Dr. Jens Winkler

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. Please describe as succinctly as possible: - What happened. - What you thought should have happened. - Precisely what you were doing at the time. Please also include any C or lisp back-traces that you may have. ================================================================ Dear Bug Team! I tried to compile the new release 21.4.6 under actual cygwin (1.3.6). uname -a: CYGWIN_NT-5.0 LETA 1.3.6(0.47/3/2) 2001-12-08 17:02 i686 unknown I used the patch xemacs-21.4.5-21.4.6.patch.gz, make distclean configure --with-dragndrop --with-x11=no make It failed with: fileio.c: In function `Fexpand_file_name': fileio.c:955: `CBufbyte' undeclared (first use in this function) fileio.c:955: (Each undeclared identifier is reported only once fileio.c:955: for each function it appears in.) fileio.c:955: parse error before `)' make[1]: *** [fileio.o] Error 1 make[1]: Leaving directory `/usr/src/xemacs-21.4.6/src' make: *** [src] Error 2 Jens

2 participants
1 comments

mainline (21.5) windows native compile problem 22 years, 3 months

Damon Lipparelli

I had to add the following to "lib-src/etags.c" to build with Win32. -lipp --- Cut Here --- Index: etags.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lib-src/etags.c,v retrieving revision 1.27 diff -u -r1.27 etags.c --- etags.c 2001/12/20 07:58:19 1.27 +++ etags.c 2001/12/24 06:00:54 ＠＠ -55,6 +55,11 ＠＠ # ifndef PTR # define PTR void * # endif +# if defined(__STDC__) +# define __P(args) args /* use prototypes */ +# else +# define __P(args) () /* no prototypes */ +# endif #else # if defined(__STDC__) && (__STDC__ || defined(__SUNPRO_C)) # define __P(args) args /* use prototypes */ --- Cut Here ---

1 participants
0 comments

Can not build php-mode.el from CVS 22 years, 3 months

Vin Shelton

Trying to build the packages from the latest CVS sources, I'm getting the following error when I 'make bindist': make[2]: Entering directory `/opt/build/xemacs-packages-2001-12-19/xemacs-packages/prog-modes' xemacs -no-autoloads -batch -l /opt/build/xemacs-packages-2001-12-19/package-compile.el -- mail-lib xemacs-devel xemacs-base cc-mode ps-print-nomule fsf-compat edit-utils ediff emerge efs vc speedbar dired -- asm-mode.el ... Wrote /opt/build/xemacs-packages-2001-12-19/xemacs-packages/prog-modes/old-c-mode.elc Done xemacs -no-autoloads -batch -l /opt/build/xemacs-packages-2001-12-19/package-compile.el -- mail-lib xemacs-devel xemacs-base cc-mode ps-print-nomule fsf-compat edit-utils ediff emerge efs vc speedbar dired -- php-mode.el Loading /usr/local/xemacs/lib/xemacs-21.4.6/lisp/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/dired/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/speedbar/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/vc/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/efs/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/emerge/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/ediff/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/edit-utils/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/fsf-compat/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/ps-print-nomule/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/cc-mode/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/xemacs-base/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/xemacs-devel/auto-autoloads... Loading /opt/build/xemacs-packages-2001-12-19/xemacs-packages/mail-lib/auto-autoloads... Compiling /opt/build/xemacs-packages-2001-12-19/xemacs-packages/prog-modes/php-mode.el... While compiling php-mode in file /opt/build/xemacs-packages-2001-12-19/xemacs-packages/prog-modes/php-mode.el: ** reference to free variable cc-imenu-php-generic-expression While compiling toplevel forms: ** reference to free variable php-mode-map ** reference to free variable php-mode-abbrev-table !! End of file or stream ((#<buffer " *Compiler Input*">)) backtrace(nil t) # bind (error-info) byte-compile-report-error((end-of-file #<buffer " *Compiler Input*">)) # bind (error-info) #<compiled-function (error-info) "...(4)" [error-info byte-compile-report-error] 2>((end-of-file #<buffer " *Compiler Input*">)) read(#<buffer " *Compiler Input*">) # (unwind-protect ...) #<compiled-function nil "...(43)" [byte-compile-unresolved-functions byte-compile-inbuffer 1 " \n" nil looking-at ";" byte-compile-file-form read byte-compile-flush-pending byte-compile-warn-about-unresolved-functions] 3>() # (unwind-protect ...) call-with-condition-handler(#<compiled-function (error-info) "...(4)" [error-info byte-compile-report-error] 2> #<compiled-function nil "...(43)" [byte-compile-unresolved-functions byte-compile-inbuffer 1 " \n" nil looking-at ";" byte-compile-file-form read byte-compile-flush-pending byte-compile-warn-about-unresolved-functions] 3>) # (unwind-protect ...) # bind (byte-compile-warnings-beginning byte-compile-point-max-prev byte-compile-log-buffer byte-compile-macro-environment byte-compile-function-environment byte-compile-autoload-environment byte-compile-unresolved-functions byte-compile-bound-variables byte-compile-free-references byte-compile-free-assignments byte-compile-verbose byte-optimize byte-compile-emacs19-compatibility byte-compile-dynamic byte-compile-dynamic-docstrings byte-compile-warnings byte-compile-file-domain byte-compile-outbuffer float-output-format case-fold-search print-length print-level byte-compile-constants byte-compile-variables byte-compile-tag-number byte-compile-depth byte-compile-maxdepth byte-compile-output eval filename byte-compile-inbuffer) byte-compile-from-buffer(#<buffer " *Compiler Input*"> "/opt/build/xemacs-packages-2001-12-19/xemacs-packages/prog-modes/php-mode.el") # bind (byte-compile-current-file target-file input-buffer output-buffer byte-compile-dest-file load filename) byte-compile-file("php-mode.el") byte-code("..." [file byte-compile-file t] 2) # (condition-case ... . ((error (byte-code "ÂÃ!Â!ÂÄ!ÅÆ!«Æ Ç\"ªÂ ＠ÈN® ＠!ÉÊ A\"ÂË!Ç" ... 3)))) # bind (file) batch-byte-compile-1("php-mode.el") # bind (error file-to-process) batch-byte-compile-one-file() # bind (error) batch-byte-compile() # bind (current-load-list) # (unwind-protect ...) # bind (load-file-name) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) load-internal("/opt/build/xemacs-packages-2001-12-19/package-compile.el" nil t nil nil nil) # bind (nosuffix nomessage noerror file) load("/opt/build/xemacs-packages-2001-12-19/package-compile.el" nil t) # bind (file arg) command-line-do-load("-l") # bind (dir file-count line end-of-options file-p arg tem) command-line-1() # bind (command-line-args-left) command-line() # (unwind-protect ...) normal-top-level() # (condition-case ... . error) # (catch top-level ...) >>Error occurred processing php-mode.el: End of file or stream: #<buffer " *Compiler Input*"> Done make[2]: *** [php-mode.elc] Error 1 make[2]: Leaving directory `/opt/build/xemacs-packages-2001-12-19/xemacs-packages/prog-modes' make[1]: *** [prog-modes/bindist.target] Error 2 make[1]: Leaving directory `/opt/build/xemacs-packages-2001-12-19/xemacs-packages' make: *** [xemacs-packages/bindist.target] Error 2 TIA, vin

4 participants
17 comments

Re: [PATCH APPROVE COMMIT] Remove ^M from php-mode.el 22 years, 3 months

Steve Youngs

|--==> "VS" == Vin Shelton <acs(a)xemacs.org> writes: VS> Steve Youngs <youngs(a)xemacs.org> writes: >>|--==> "VS" == Vin Shelton <acs(a)xemacs.org> writes: >> VS> Every line in php-mode.el ended in ^M. Once I removed all of the VS> ^M's, php-mode.el byte-compiled fine. >> >>Good. >> >>Vin, can you do me a huge favour, please? Commit the ^M-less >>php-mode.el to CVS. >> >>Thanks heaps, Vin. VS> Anyway, Steve, here is the patch you requested. I think we've been VS> down this road before, see VS> http://list-archive.xemacs.org/xemacs-patches/200107/msg00014.html Yeah, I remember that. One of the reasons I asked you to commit this.:-) VS> how are these ^M's getting inserted? My suspicion is that the file was at one stage edited on Windoze *<shudder>*. In this instance, by the upstream. Thanks for doing this, Vin. I'll revert my patch that attempted to fix the problem (escape a '('), because, as Steve T said, it shouldn't be necessary. New prog-modes shortly. -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------<youngs(a)xemacs.org>---|

1 participants
0 comments

how to put a menu into _all_ menubars? 22 years, 3 months

Sean Champ

i'm trying to get a menu into all the menubars of the live buffers, and into the default menubar that will be put used with new buffers. the following code looks like it should be working, even without the second `set-menubar' form, but it's still not getting the Taskit menu into all of the danged menubars. (require 'cl) (fset 'taskit-root-menu-filler 'ignore) (defun taskit-install-menu () (or (assoc "Taskit" default-menubar) (let ((posn (or (position "%_Options" default-menubar :key #'car :test #'string=) 6))) (set-menubar ;; hell. this doesn't install it in the menubars ;; of currently active buffers. (append (subseq default-menubar 0 posn) (list* (list "Taskit" :filter #'taskit-root-menu-filler) (nthcdr posn default-menubar))))) (dolist (buff (buffer-list)) ;; double hell. this doesn't install it in the menubars ;; of all buffers, either. (set-buffer buff) (add-submenu nil (list "Taskit" :filter #'taskit-root-menu-filler) "Options" 'current-menubar))) ;; and, finally, we get to repeat ourselves for the second time. ;; and it STILL doesn't get the menu into all of the menu-bars. (add-submenu nil (list "Taskit" :filter #'taskit-root-menu-filler) "Options" )) (taskit-install-menu) ;; and, for convenience' sake: (defun taskit-uninstall-menu () (set-menubar (remassoc "Taskit" default-menubar)) (dolist (buffer (buffer-list)) (set-buffer buffer) (set-menubar (remassoc "Taskit" current-menubar)))) ;; EOsnip this is not-working on xemacs 21.4.5, with gtk widgets. what's the deal? what hoodoo does it take to get a menu into _all_ of the menubars?

1 participants
0 comments

Testing with different XEmacsen 22 years, 3 months

Steve Youngs

Hey there Everyone! Not a request or question, but an offer. I've just installed 6 different copies of XEmacs (21.1, 21.4, 21.5 - both Mule and non-mule for each). So if you want something tested on a certain XEmacs just give me a yell. Well it is the "giving" time of year. :-) -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------<youngs(a)xemacs.org>---|

1 participants
0 comments

bug : 21.4.5/gtk : segfaulting with vector as first arg to #'popup-menu 22 years, 3 months

Sean Champ

* xemacs version: xemacs 21.4.5, gtk widgets * steps to reproduce, and description: try this, when you're ok with your xemacs possibly segfaulting: (popup-menu (vector "test" #'ignore t) when evaluating that form, my xemacs segfaults. it works fine if it's like this: (popup-menu (list "menu header not shown in GTK xemacs" (vector "test" #'ignore t))) this xemacs just doesn't seem to like a vector as the first arg on popup-menu * suggested fix: somewhere in the popup-menu defun: (check-argument-type #'listp menu-description) ..or whatever C equivalent -- sean champ

2 participants
1 comments

for the GTK pool : gtk-read-string.el 22 years, 3 months

Sean Champ

here's a submission for the main xemacs codebase. gtk-read-string.el --- Reading a string from a GTK dialog window i'd submit a diff for it, but i have another diff to make, once i get back to synching folding.el -- this would mess it up, or vice versa; the only change would be to include the following file -- gtk-read-string.el -- in the lisp dir of the xemacs source-tree. here's a ChangeLog entry for it: 2001-12-23 Sean Champ <schamp(a)users.sourceforge.net> * gtk-read-string.el: new * gtk-read-string.el (gtk-read-string): new further work: - something could be done in 'should-use-dialog-box-p', for adding support for gtk-read-string, but i haven't taken a look at it, yet. misc notes: - there's a suggestion or two in the comments, for folks who've been thinking about programming stuff that makes use of xemacs' gtk support. (i've also been hacking around something called gtk-read-passwd, but i'm not sure how secure it'll end up being. (passwd-grab-keyboard) isn't working, for it, and i'm not sure if any input-even recording is done for gtk dialog widgets that aren't like xemacs buffer widgets.) anyway, here's something to 'read-string' with gtk widgets; any suggestions would most likely be appreciated. ;;; gtk-read-string.el --- Reading a string from a GTK dialog window ;; Copyright (C) 2000 Free Software Foundation, Inc. ;; Maintainer: Sean Champ <schamp(a)users.sourceforge.net> ;; Keywords: gtk, interface ;; This file is not an official part of XEmacs. ;; gtk-read-string.el is free software; you can redistribute it and/or modify it ;; under the terms of the GNU General Public License as published by ;; the Free Software Foundation; either version 2, or (at your option) ;; any later version. ;; gtk-read-string.el is distributed in the hope that it will be useful, but ;; WITHOUT ANY WARRANTY; without even the implied warranty of ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU ;; General Public License for more details. ;; You should have received a copy of the GNU General Public License ;; along with gtk-read-string.el; see the file COPYING. If not, write to the ;; Free Software Foundation, 59 Temple Place - Suite 330, ;; Boston, MA 02111-1307, USA. ;;; Synched up with: Not in FSF. (provide 'gtk-read-string) (require 'cl) (defun* gtk-read-string (prompt &optional initial-contents history default-value &key window-title &key prompt-align-left) "Return a string which will be read from a GTK dialog widget, prompting with string PROMPT. If non-nil, optional second arg INITIAL-CONTENTS is a default string to insert in the entry area, which will be returned if the user presses the 'cancel' button before entering any text. In such a case, INITIAL-CONTENTS will be added to the history. note: When INITIAL-CONTENTS is not specified, This function counts \"the user entered nothing\" as being equivalent to \"the user entered a zero-width string\". Third arg HISTORY, if non-nil, should name a variable which contains a list, to which the return-value will be prepended, unless the return-value equals the DEFAULT-VALUE; see below. Fourth arg DEFAULT-VALUE will be returned, if either the DEFAULT-VALUE, or what the user entered, was a zero-width string. In such a case, the value, being equivalent to DEFAULT-VALUE, will not be added to the history. The optional keyword :window-title may be used in setting the title of the dialog window. Optional keyword :prompt-align-left, if specified with a non-nil value, will cause the PROMPT to be aligned against the left of its label-area in the dialog box, rather than in the center. also see: `read-string' " ;; written with `gtk-password-dialog' as an initial example ;; something in the doc-string is screwing up the automatic indentation. (let ((returnv (block dialog ;; set up and show the dialog and all its child widgets. ;; ;; the string value is fetched as a result of ;; (return-from dialog ... ) in the callback that will be attatched ;; to the "OK" and "Cancel" buttons, and to the 'destroy' signal ;; on the dialog window itself. (let* ((widget) (dialog (gtk-dialog-new)) (vbox (gtk-dialog-vbox dialog)) (button-area (gtk-dialog-action-area dialog)) (callback #'(lambda (button dialog) (gtk-main-quit) (gtk-widget-destroy dialog) (return-from dialog (gtk-entry-get-text (get dialog 'x-initial-entry)))))) (gtk-window-set-title dialog (or window-title (format "%S : %S" (emacs-name) prompt))) ;; NOTE: XEmacs GTK programmers: if you call `gtk-main', ;; after showing a dialog, as it's done in this function, ;; ALWAYS connect {something} to the 'destroy' event ;; on the dialog you showed, and make sure that the {something} ;; will call `gtk-main-quit'; if you don't, then xemacs ;; will just get stuck in the `gtk-main' loop, when ;; the user closes the window. (gtk-signal-connect dialog 'destroy callback dialog) ;; "make us modal" (???) [comment from gtk-password-dialog] (put dialog 'type 'dialog) (setq widget (gtk-button-new-with-label "OK")) (gtk-container-add button-area widget) (gtk-signal-connect widget 'clicked callback dialog) (put dialog 'x-ok-button widget) ;; Note: some of these x-foo-bar properties are used in ;; gtk-password-dialog.el, for making functions that access some of the ;; widgets that compose the dialog; a similar thing could've been done ;; here, but gtk-read-password is a fairly high-level function. (gtk-widget-show widget) (setq widget (gtk-button-new-with-label "Cancel")) (gtk-container-add button-area widget) (gtk-signal-connect widget 'clicked callback dialog) (put dialog 'x-cancel-button widget) (gtk-widget-show widget) ;; the prompt (gtk-container-set-border-width vbox 5) (setq widget (gtk-label-new prompt)) (and prompt-align-left (gtk-misc-set-alignment widget 0.0 0.5)) (gtk-container-add vbox widget) (gtk-widget-show widget) ;; the widget where the string is entered (setq widget (gtk-entry-new)) (gtk-container-add vbox widget) (put dialog 'x-initial-entry widget) (gtk-widget-show widget) (when initial-contents (gtk-entry-set-text (get dialog 'x-initial-entry) initial-contents) (gtk-entry-select-region (get dialog 'x-initial-entry) 0 (length initial-contents))) (gtk-widget-show dialog) (gtk-main) )))) ;; end of 'let' bindings (and default-value (zerop (string-width returnv)) (setq returnv default-value)) ;; don't add it to the history, if it equals the default-value (and history (or (and default-value (string= returnv default-value)) (set history (cons returnv (symbol-value history))))) returnv)) ;; gtk-read-string.el ends here

2 participants
1 comments

Error building xemacs-21.4.6/man/lispref.dvi 22 years, 4 months

José Romildo Malaquias

Hello. Trying to build the Lisp Reference manual in DVI format from xemacs-21.4.6/man gives some error messages reported below. It would be nice if somebody could correct these errors. My computer is running RedHat Linux 7.2 with latest updates. $ cd xemacs-21.4.6/man $ make clean $ make lispref.dvi texi2dvi -I lispref lispref/lispref.texi This is TeX, Version 3.14159 (Web2C 7.3.1) [...] Transcript written on lispref.log. This is TeX, Version 3.14159 (Web2C 7.3.1) (/home/romildo/rpmbuild/BUILD/xemacs-21.4.6/man/lispref/lispref.texi (texinfo.tex Loading texinfo [version 1999-09-25.10]: Basics, pdf, fonts, page headings, tables, conditionals, indexing, sectioning, toc, environments, defuns, macros, cross references, (/usr/share/texmf/tex/plain/dvips/epsf.tex) localization, and turning on texinfo input format.) (lispref.aux ! Undefined control sequence. <argument> The User＠s View-title ＠xrdef ...＠endgroup ＠expandafter ＠gdef ＠csname X#1 ＠endcsname l.52 'xrdef {The User's View-title} {The User's View} ? ! Undefined control sequence. <argument> The User＠s View-pg ＠xrdef ...＠endgroup ＠expandafter ＠gdef ＠csname X#1 ＠endcsname l.53 'xrdef {The User's View-pg} {17} ? ! Undefined control sequence. <argument> The User＠s View-snt ＠xrdef ...＠endgroup ＠expandafter ＠gdef ＠csname X#1 ＠endcsname l.54 'xrdef {The User's View-snt} {Section'tie3.1} ? ! Undefined control sequence. <argument> The Library Maintainer＠s View-title ＠xrdef ...＠endgroup ＠expandafter ＠gdef ＠csname X#1 ＠endcsname l.55 'xrdef {The Library Maintainer's View-title} {The Library Maintainer's V... ? ! Undefined control sequence. <argument> The Library Maintainer＠s View-pg ＠xrdef ...＠endgroup ＠expandafter ＠gdef ＠csname X#1 ＠endcsname l.56 'xrdef {The Library Maintainer's View-pg} {19} ? ! Undefined control sequence. <argument> The Library Maintainer＠s View-snt ＠xrdef ...＠endgroup ＠expandafter ＠gdef ＠csname X#1 ＠endcsname l.57 'xrdef {The Library Maintainer's View-snt} {Section'tie3.2} ? ! Undefined control sequence. <argument> The Package Release Engineer＠s View-title ＠xrdef ...＠endgroup ＠expandafter ＠gdef ＠csname X#1 ＠endcsname l.67 ...The Package Release Engineer's View-title} {The Package Release Engin... ? ! Undefined control sequence. <argument> The Package Release Engineer＠s View-pg ＠xrdef ...＠endgroup ＠expandafter ＠gdef ＠csname X#1 ＠endcsname l.68 ...f {The Package Release Engineer's View-pg} {22} ? ! Undefined control sequence. <argument> The Package Release Engineer＠s View-snt ＠xrdef ...＠endgroup ＠expandafter ＠gdef ＠csname X#1 ＠endcsname l.69 ... {The Package Release Engineer's View-snt} {Section'tie3.2.4} ? ) [1] [2] (/home/romildo/rpmbuild/BUILD/xemacs-21.4.6/man/lispref/intro.texi [...] Output written on lispref.dvi (936 pages, 3763024 bytes). Transcript written on lispref.log. /usr/bin/texi2dvi: tex exited with bad status, quitting. /usr/bin/texi2dvi: see lispref.log for errors. make: *** [lispref.dvi] Error 1 Regards, Romildo -- Prof. José Romildo Malaquias Departamento de Computação http://iceb.ufop.br/~romildo Universidade Federal de Ouro Preto romildo(a)iceb.ufop.br Brasil romildo(a)uber.com.br

1 participants
0 comments

gdb/cygwin/xemacs/w2000 problem 22 years, 4 months

jasmuth

I couldn't (and was warned not to) go back to cygwin 1.3.2. Could it be that you have the CYGWIN environment variable set to something special? (http://cygwin.com/cygwin-ug-net/using-cygwinenv.html) How do I go about getting this problem resolved? It seems I am the only one having it. I reposted to comp.emacs.xemacs again and still have no responses? THanks, Jane ----- Original Message ----- From: "Jane Asmuth" <jasmuth(a)sarnoff.com> To: <xemacs-beta(a)xemacs.org>; "Andy Piper" <andy(a)xemacs.org> Sent: Tuesday, December 18, 2001 4:30 PM Subject: Re: XEmacs 21.4.6 "Common Lisp (Windows)" is released > I am using cygwin 1.3.5. I also just tried 1.3.6 and it doesn't work > either. > I will attempt to reinstall 1.3.2 and see if that helps. > > Thanks, > Jane > > ----- Original Message ----- > From: "Andy Piper" <andy(a)xemacs.org> > To: "JANE ASMUTH" <jasmuth(a)sarnoff.com>; <xemacs-beta(a)xemacs.org> > Sent: Tuesday, December 18, 2001 3:33 PM > Subject: Re: XEmacs 21.4.6 "Common Lisp (Windows)" is released > > > > At 02:39 PM 12/18/2001 -0500, JANE ASMUTH wrote: > > >I have been having a problem with gdb/cygwin/xemacs for the past several > > >months. I have posted numerous messages on newsgroups, but have never > > >gotten any response. I am emailing my question to you in the hopes that > you > > >can either help me or point me to a resource where I can get help.... > > > > > >I want to use gdb with xemacs to debug c++ programs using the > > >Windows2000/cygwin environment. I was able to do this (debug with gdb) > > >with previous versions of xemacs, but can't since I updated my version > > >several months ago. What happens is that the output of my program is > > >directed to an external pop-up dos window instead of the gdb console > frame. > > >I found some references to a problem similar to mine at > > >http://www.cygwin.com/ml/cygwin/2001-03/msg00714.html > > > > > >Has anyone else reported this problem with using gdb via xemacs 21.4.x? > If > > >not then, maybe I have a problem with my setup? > > > > This works for me using XEmacs 21.4.6 built using cygwin. I am using > cygwin > > 1.3.2 > > > > andy > > > > >

2 participants
1 comments

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 December 2001