August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

William M. Perry

I'm going to be in dublin and cork and just in general cruising around ireland Oct 20 - 29th this year... if anybody wants to get together for a few pints, give me a yell. Probably spend more time in cork than in dublin. -bp

1 participants
0 comments

Re: user-init-directory set to "/.xemacs/" instead of "~/.xemacs/" 24 years, 9 months

Jan Vroonhof

karlheg(a)cathcart.sysc.pdx.edu (Karl M. Hegbloom) writes: > It looks like `user-init-directory', as Stef points out, is > initialized to just "/.xemacs/", and is later used in combination > with `init-file-user' to form the filename path in > `load-user-init-file'. "package-get.el" just sets > `package-get-user-package-location' to `user-init-directory'. Yes, my mistake. > This stuff needs to be gone over, I think. `user-init-directory' > really ought to bear the `~' prefix; but the `init-file-user' thing > has to keep working. Indeed. user-init-directory just needs to be constructed at run time. It is confusing that user-init-directory isn't the full path, but user-init-file is. > I'm a little angry that the `init.el' and `.options.el' stuff got > backed out. Why was that done? Because at the time of the feature freeze there were still some problems with it and it was decided it needed more time to become stable and thus it was postponed. With hindsight that was probably a bad idea (we broke backwards compatibility anyway with the options menu). The main issue is not compatibility with FSF emacs. It is compatibility with older XEmacsen. That is important and that is why it is probably imperative to fall back on .emacs if that exists. The other issue is proper migration of the customize stuff. I have some ideas how to that. > email the author and it would be changed by the end of next week. I > will submit patches for this if they will be accepted. If you want to see this feature in 21.2 (I want it too) it is better to get it in as early as possible. However you need to give more though to migration issues before it can go in. Jan

1 participants
0 comments

Re: user-init-directory set to "/.xemacs/" instead of "~/.xemacs/" 24 years, 9 months

Karl M. Hegbloom

>>>>> "Stef" == Stef Epardaud <stef(a)lunatech.com> writes: Stef> i'm using package-get to update my packages, and each time, Stef> i'm prompted to update the package list in a subdir of Stef> "/.xemacs", now i don't know how many of you have a .xemacs Stef> dir in the root dir but i suspect not many. in startup.el, Stef> it is set to : (defconst user-init-directory "/.xemacs/" Stef> "Directory where user-installed packages may go.") Stef> and i would therefore assume that code using this variable Stef> would prepend the missing '~' but not many packages use this Stef> variable in elisp, just where-was-i-db and package-get it Stef> seems. anyways, i can set it for myself, but i think that Stef> either it should be a default to put the '~' or code using Stef> it should prepend it ? after all it is very unlikely to Stef> have anything located in "/.xemacs/" right ? It looks like `user-init-directory', as Stef points out, is initialized to just "/.xemacs/", and is later used in combination with `init-file-user' to form the filename path in `load-user-init-file'. "package-get.el" just sets `package-get-user-package-location' to `user-init-directory'. This stuff needs to be gone over, I think. `user-init-directory' really ought to bear the `~' prefix; but the `init-file-user' thing has to keep working. I'm a little angry that the `init.el' and `.options.el' stuff got backed out. Why was that done? GNU Emacs and XEmacs often have incompatible configuration options. When you start one or the other using config files tainted by the other, it produces errors and an incomplete startup. It's not very difficult to run a grep and find ".emacs", then go there and edit the manuals and whatever else. If an "oreilly book says .emacs" then tough; the book's on paper or we'd email the author and it would be changed by the end of next week. I will submit patches for this if they will be accepted.

1 participants
0 comments

How to achieve context-sensitive char syntax? 24 years, 9 months

Adrian Aichner

Hello All, I try to define a syntax table for a language which uses " for string-quotes. Inside of strings " is used to char-quote ". To get a string of two consecutive double-quotes one would write: """""" My conclusion is that this cannot be done with elisp syntax tables. Am I correct? Any suggestions? Regards, Adrian

3 participants
2 comments

XEmacs in the gutter (Re: gutter fixes) 24 years, 9 months

SL Baur

[Sorry for the pun, but someone had to do it. :-)] Andy Piper <andy(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > At 10:45 AM 8/6/99 +0900, Stephen J. Turnbull wrote: ... >> Repainting the gutter still seems to clear an excessively large area >> though. ;; I see this too. > I think this is a problem with the tab widget. When adding or > removing tabs from the widget they seem to all get squashed > vertically before they sort themselves out. Indeed, that appears to be the case. > I have told Ed Falk - but no reply as yet. Hell, we have the code. If > anyone knows about Xt widgets they could take a look.... There still seem to be some problems. I am now running Gnus in an XEmacs with tabs. In this *wide reply to Andy Piper...* message buffer I see only one tab labelled `.dgnusrc-newshost-dribble' (the Gnus dribble file). Ideally, that buffer shouldn't get a tab at all. I do not see tabs for the *Summary* and *Topics* buffers. They _should_ have tabs. Are you restricting tabs to only buffers that have files behind them? I have experimented some more with multiple windows and I don't like the way they are handled. For example, if I have three windows A, B, C and the text cursor is in A, clicking on the B tab replaces the contents of A's with B. This doesn't seem very useful to me. I think I would prefer (as an option) to have the text cursor moved C-x o style if the buffer is already being displayed in a window on that frame. Another possibility might be to only show tabs for buffers that don't have windows. Er, what happened to the tab for the *scratch* buffer? That's generally a buffer I like to switch to quite often. What is supposed to happen when there are too many buffers to fit in the display? Will you add some method of scrolling the buttons?[1] I'm going to run this way for awhile and see how I like it. Footnotes: [1] Which reminds me. We really need to revive the scrolling modeline patch. I still have a great need for seeing the right side of the modeline, and generally I can't.

2 participants
1 comments

Re: [Ilya Zakharevich <ilya@math.ohio-state.edu>] Re: Outdated cperl-mode in 5.005_58 24 years, 9 months

Jan Vroonhof

"Matthew O. Persico" <mpersico(a)erols.com> writes: > and just slap it over my sumo unwind. I am now on 21.2.19 of xemacs. The > only problem I see is when you try to do a perldoc - his code looks for a > function called Man-get-page-in-background, which is probably FSF. > > Any ideas on the corresponding XEmacs call? manual-entry (and the name of the program to call is 'Manual-program'). Jan P.S. I found some of my work again. This is the patch I made to get cperl to respect the delete-key-deletes-forward issues under XEmacs. Could you please try to get this by Ilya once more and then submit a version to XEmacs-patches ? diff -u /u/users/vroonhof/emacs/lisp/cperl-mode.el.4.5 /u/users/vroonhof/emacs/lisp/cperl-mode.el --- /u/users/vroonhof/emacs/lisp/cperl-mode.el.4.5 Fri Aug 6 12:39:43 1999 +++ /u/users/vroonhof/emacs/lisp/cperl-mode.el Fri Aug 6 12:39:43 1999 ＠＠ -800,6 +800,10 ＠＠ ;;; `constant-face' was backward. ;;; (`font-lock-other-type-face'): Done via `defface' too. +;;; After 4.5 +;;; (`cperl-set-conformant-backward-deletion'): Follow policy of the +;;; Emacs version + ;;; Code: ＠＠ -847,6 +851,7 ＠＠ (cperl-make-face (, arg) (, descr))) (or (boundp (quote (, arg))) ; We use unquoted variants too (defconst (, arg) (quote (, arg)) (, descr)))))))) + (require 'custom) (defun cperl-choose-color (&rest list) ＠＠ -1537,7 +1542,8 ＠＠ ;;; Portability stuff: -(defconst cperl-xemacs-p (string-match "XEmacs\\|Lucid" emacs-version)) +(defconst cperl-xemacs-p (or (featurep 'xemacs) + (string-match "XEmacs\\|Lucid" emacs-version))) (defmacro cperl-define-key (emacs-key definition &optional xemacs-key) (` (define-key cperl-mode-map ＠＠ -1551,6 +1557,16 ＠＠ (where-is-internal 'backward-delete-char-untabify))) "Character generated by key bound to delete-backward-char.") +(defvar cperl-backward-delete-function nil) + +(defmacro cperl-set-conformant-backward-deletion (func) + `(if (not (boundp 'backward-delete-function)) + (cperl-define-key "\177" ,func) + ;; we do not clobber backspace on standard Emacs, why? + (setq cperl-backward-delete-function ,func) + (define-key cperl-mode-map [backspace] ,func) + (setq cperl-del-back-ch 'backspace))) + (and (vectorp cperl-del-back-ch) (= (length cperl-del-back-ch) 1) (setq cperl-del-back-ch (aref cperl-del-back-ch 0))) ＠＠ -1681,7 +1697,7 ＠＠ [(control meta |)]) ;;(cperl-define-key "\M-q" 'cperl-fill-paragraph) ;;(cperl-define-key "\e;" 'cperl-indent-for-comment) - (cperl-define-key "\177" 'cperl-electric-backspace) + (cperl-set-conformant-backward-deletion 'cperl-electric-backspace) (cperl-define-key "\t" 'cperl-indent-command) ;; don't clobber the backspace binding: (cperl-define-key "\C-c\C-hF" 'cperl-info-on-command ＠＠ -2126,6 +2142,9 ＠＠ (make-local-variable 'vc-header-alist) (set 'vc-header-alist cperl-vc-header-alist) ; Avoid warning (make-local-variable 'font-lock-defaults) + (when cperl-backward-delete-function + (make-local-variable 'backward-delete-function) + (setq backward-delete-function cperl-backward-delete-function)) (setq font-lock-defaults (cond ((string< emacs-version "19.30")

1 participants
0 comments

current-pixel-column #2 24 years, 9 months

Andy Piper

This then? Maybe someone could try it out to see if it does what they want... andy -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

Re: gutter fixes 24 years, 9 months

SL Baur

[I have a clean --with-widgets=athena3d build with the configuration I just posted. It builds and it hasn't crashed under the very light testing I've done so far -- that's a start.] Andy Piper <andy(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > At 05:35 PM 8/4/99 +0200, Adrian Aichner wrote: >> After starting XEmacs it has only one tab for "*scratch*". >> >> I type >> C-x C-b (list-buffers) >> which gives me "*Buffer List*" in the lower window. >> >> No new tab for that buffer is created until I >> M-: (update-tab-in-gutter) I can duplicate this on Unix. However, there is more strange behavior. If I run the `update-tab-in-gutter' with part of the XEmacs frame obscured, the gutter gets continually updated until the frame is brought to the front. Hitting C-g does not appear to stop it. > Hmmn, I need to fix up split-window handling. Yes. Here's another wierd effect. (Observed with both Athena Widgets and Motif Widgets). After doing C-x C-b do C-x o and C-x 1 (so that the only buffer shown is the *Buffer List* buffer). The bottom boundary line disappears and only the *scratch* button is shown. After doing M-: (update-tab-in-gutter) the *Buffer List* button is shown and the dividing line comes back. How is this supposed to work with split-windows? If I click on a gutter button that has a displayed window but the text cursor is in another window in the same frame, should the text cursor be moved? I'm not sure I like this or not yet, but it looks kind of cool and it might be more useful than the largely useless toolbar.

3 participants
9 comments

Re: 21.2.19 SEGV on null frame pointer 24 years, 9 months

Karl Kleinpaste

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: >> 0x4c002d9 (has no name): () 481x15+4+258 +9+279 >> 0x4c0014b (has no name): () 481x15+4+258 +9+279 > Notice how these two have exactly the same coordinates. > Maybe there is some race condition where XEmacs thinks it has deleted > the window but X still thinks it is there? Would I be correct in surmising that that geometry is the toolbar? Gnus does a heck of a lot of hackery with the toolbar. I'm guessing wildly, but perhaps Gnus was in mid-toolbar replacement when the keystroke event hit, so that one toolbar was being created while the other had yet to be destroyed, leaving inconsistent clues about active windows? Or maybe it's the menu bar, with which Gnus messes around equally.

2 participants
1 comments

Re: [Ilya Zakharevich <ilya@math.ohio-state.edu>] Re: Outdated cperl-mode in 5.005_58 24 years, 9 months

Jan Vroonhof

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > (locate-library "cperl-mode.el") > "c:\\Program Files\\XEmacs\\xemacs-packages\\lisp\\prog-modes\\cperl-mode.el" > > Are we really that far behind? Yes. I tried merging the XEmacs changes back with Ilya one but we got sidetracked somewhere (the whole discussion was cc: xemacs-beta so must be in the archive). Thus it never happened and I never got back to it (don't use perl that much anymore). I think the most important issues were 1. delete-key-deletes-forward support 2. c-perl-mode defining C-h f and C-h v. I think newer versions no longer do so by default. Maybe they are no longer relevant. It would be nice if somebody else would look into it gain. Please note that it can take quite some effort to get changes past Ilya's quality control. Jan

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 August 1999