August 1998 - XEmacs-Beta - XEmacs Mailing List Archives

MH and TM -- article-XXX buffer annoyance 26 years, 3 months

Rick Campbell

Is there anyone (else) out there using mh-e and tm together? I sometimes get this annoying behavior where the article-XXX buffer (something added by the tm interface to mh) is left in an awkward state causing me to get a slew of `do you really want to edit it' queries. I've seen it in 20.4 as well as 21.0 "Erzgeberg" so I'm assuming that it's not causing others grief, but if anyone knows of a simple fix, I'd appreciate it if they'd pass it along. Rick

2 participants
3 comments

dumb question 26 years, 3 months

Andy Piper

How do I use tm with gnus? All of the info nodes on this are empty. andy --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

1 participants
0 comments

Re: X-error in get_mouse_position 26 years, 3 months

Gunnar Evermann

Pete Ware <ware(a)cis.ohio-state.edu> writes: > Didier is right, I misstated that the phase 2 happens when all events > are processed. It happens when the current event is finished being > dispatched (i.e. XtDispatchEvent() is about to return). > > > OK, I'm about ready to give about! > What was the problem again? :-) over-reaction on my part :-) When I had sent the patch yesterday I discovered that I could reliably crash XEmacs by closing a newly created frame. As I was in a hurry I panicked and declared my patch flawed :-) More careful examination showed that this crash was not related to the patch (apparently it was caused by a (badly) miscompiled libdb.a (don't ask -- I will LART our admin right now). This lib totally fsck'ed up the XEmacs binary (dbx even reported an internal error when reading it), but it still worked, kind of. After a clean recompile everything is great now. Without the patch I get the X error and with the patch it goes away. No crashes -- everything is great now!!! Steve, if you are still reading this, please consider this patch (maybe even for 21.0?). Sorry for the confusion. Gunnar

1 participants
0 comments

Re: concat vs expand-file-name ? 26 years, 3 months

Colin Rafferty

Darryl Okahata writes: > Hrvoje Niksic <hniksic(a)srce.hr> wrote: >> Karl M. Hegbloom writes: >>> (concat (file-name-as-directory dir) file) >> This particular code works on Windows, but we might support other file >> systems where this won't work, so the code is not really being nice. > What's the reason for this? The code doesn't appear to be Unix or > Windows-specific. I've been writing code that uses `concat', and so I'd > like to know why it's not portable. Because there could be system where this is not a valid file name. While this works on Windows, Unix, and VMS, it may not always work. `expand-file-name' will always work, no matter what system it is on. -- Colin

1 participants
0 comments

w3 on native-build mswindows 26 years, 3 months

Jonathan Harris

The enclosed patch against package version 1.06 of w3 makes w3 mostly work on the native mswindows build of XEmacs. The patched function url-basepath has actually changed since 1.06 so this patch won't apply, but that's OK beause I'm really just asking for advice. The problem that the patch fixes is that w3 calls XEmacs path handling functions on URL paths. That doesn't work under mswindows because these path handling functions convert path separators into '\\' because that is the native path separator on Win32. The attached patch replaces two occurrences in url-basename of such calls with manual string-matches. There are a lot more calls to XEmacs path handling functions in w3. Many of these calls are fine on mswindows because they're being called on local pathnames of files. Probably there are other calls where the pathname in question is actually the pathname component of a URL, and these will break on mswindows. Is there any structuring in the w3 files that will enable me to go about identifying all such calls that will break, or do I really have to examine _every_ single call to XEmacs path handling functions? Alternatively, is there a better approach than manually replacing selective calls to XEmacs path handling functions with string matches? Jonathan. -- Jonathan Harris | jhar(a)tardis.ed.ac.uk London, England | Jonathan.Harris(a)symbian.com --- url.el.bak Tue Apr 28 04:05:23 1998 +++ url.el Thu Jul 30 18:39:36 1998 ＠＠ -1233,8 +1233,13 ＠＠ "Return the base pathname of FILE, or the actual filename if X is true" (cond ((null file) "") - (x (file-name-nondirectory file)) - (t (file-name-directory file)))) + (x + (if (string-match "[^/]*$" file) + (match-string 0 file) + file)) + (t + (if (string-match ".*/" file) + (match-string 0 file))))) (defun url-parse-query-string (query &optional downcase) (let (retval pairs cur key val)

4 participants
3 comments

Re: concat vs expand-file-name ? 26 years, 3 months

Hrvoje Niksic

karlheg(a)inetarena.com (Karl M. Hegbloom) writes: > In `pcl-cvs.el', at line 503, it goes: > > (COLLECT > ;; for viewing *match-list*, uncomment this and run > ;; (debug) > (let* > ((c (car (car *match-list*))) ; Is using `concat' acceptable here? > (full-path (concat (file-name-as-directory *root-dir*) > (car (cdr (car *match-list*))))) > > ... wasn't there something about not useing `concat' like that, for > Windows compatiblility reasons? This particular code works on Windows, but we might support other file systems where this won't work, so the code is not really being nice. > Should this be changed then, I wonder? No reason to change it now. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- We are all just prisoners here of our own MAKEDEV.

2 participants
1 comments

Re: Is anyone using gud? 26 years, 3 months

Hrvoje Niksic

Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes: > >>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: > > sb> There's gdb.el/gdbsrc.el for GDB and the EOS stuff for DBX. Is anyone > sb> using gud? Is the XEmacs version usable? > > One colleague of mine tried to use it a couple of weeks ago and he > commented about the lack of completion on function names (when you > set a breakpoint for instance) which exists in FSF Emacs. Yeah, but the same goes for our gdb mode, doesn't it? Are you sure he was actually using gud, as opposed to the plain gdb mode? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- The Lord protects children and fools... But don't push it.

1 participants
0 comments

Re: Is anyone using gud? 26 years, 3 months

Oscar Figueiredo

>>>>> "sb" == SL Baur <steve(a)xemacs.org> writes: sb> There's gdb.el/gdbsrc.el for GDB and the EOS stuff for DBX. Is anyone sb> using gud? Is the XEmacs version usable? One colleague of mine tried to use it a couple of weeks ago and he commented about the lack of completion on function names (when you set a breakpoint for instance) which exists in FSF Emacs. For the rest it seemed usable. I didn't have time to have a look at it myself. Oscar

1 participants
0 comments

concat vs expand-file-name ? 26 years, 3 months

Karl M. Hegbloom

In `pcl-cvs.el', at line 503, it goes: (COLLECT ;; for viewing *match-list*, uncomment this and run ;; (debug) (let* ((c (car (car *match-list*))) ; Is using `concat' acceptable here? (full-path (concat (file-name-as-directory *root-dir*) (car (cdr (car *match-list*))))) ... wasn't there something about not useing `concat' like that, for Windows compatiblility reasons? Should this be changed then, I wonder?

1 participants
0 comments

Re: Make custom-faces all order more sensible 26 years, 3 months

Karl M. Hegbloom

What's wrong with just using the ubiquitous `C-s'? C-s runs `isearch-forward' `isearch-forward' is an interactive compiled Lisp function -- loaded from "/usr/local/src/XEmacs/xemacs-21-Finnish_Landrace/lisp/isearch-mode.elc" (isearch-forward &optional REGEXP-P) Documentation: Do incremental search forward. With a prefix argument, do an incremental regular expression search instead. As you type characters, they add to the search string and are found.

1 participants
0 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 August 1998