October 2010 - XEmacs-Beta - XEmacs Mailing List Archives

GPLv3/L8R -- The lwlib files that are part of Lucid Widget Library? 14 years

The XEmacs Package Smoketest

Hi, I guess that the files that are in the lwlib directory and has a license starting with "This file is part of the Lucid Widget Library" shall continue to be part of the Lucid Widget Library when we convert to GPLv3 or later? The license shall _not_ be changed to "This file is part of XEmacs..."? (I have this problem with understanding how things can be in the XEmacs distribution/repo/built with but still part of something else. If you want to explain this to me fine. If you don't that is fine too. I just want to do the right thing here so I don't really have to understand just as long I do that, eg the right thing ;-) Yours -- %% Mats _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

problem with region-based functions which prompt for args in the minibuffer 14 years

Greg Klanderman

All the region-based functions that prompt for arguments in the minibuffer I can think of suffer from the same problem, which is that the region is lost if while entering an argument in the minibuffer you happen to use C-y (yank) or jump out of the minibuffer with C-o, problem being that the region extent is not grabbed until after the interactive arguments are read. For example, highlight a region and use any of the {query-,}replace-* commands. When prompted for the string to replace, yank the text you just copied and the region is lost and now the operation applies to the rest of the file rather than the intended region. The same happens if you leave the minibuffer, for example to copy the string you want to enter. Similarly, if you try to prefix-region and yank the prefix string, you get an error because the region is not active by the time it's needed. Is there some general solution which would allow the region to be saved and restored while evaluating the interactive declaration? Greg _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

Summary of XEmacs Issue Tracking System Issues 14 years, 1 month

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2010-10-19 - 2010-10-26) XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 496 open ( +5) / 238 closed ( +0) / 734 total ( +5) Open issues with patches: 11 Average duration of open issues: 693 days. Median duration of open issues: 696 days. Open Issues Breakdown new 169 ( +1) deferred 6 ( +0) napping 4 ( +0) verified 49 ( +3) assigned 154 ( +1) committed 25 ( +0) documented 2 ( +0) done/needs work 24 ( +0) Issues Created Or Reopened (5) ______________________________ Make repeated mark-backward commands work 2010-10-23 http://tracker.xemacs.org/XEmacs/its/issue732 created stephen Change the process is "only of interest to" to "should only be 2010-10-23 http://tracker.xemacs.org/XEmacs/its/issue733 created stephen cedet does not seem to work 2010-10-24 http://tracker.xemacs.org/XEmacs/its/issue734 created graaff sexp functions don't grok #<> expressions 2010-10-26 http://tracker.xemacs.org/XEmacs/its/issue735 created stephen prettyprinters are ugly 2010-10-26 http://tracker.xemacs.org/XEmacs/its/issue736 created stephen _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: Idle functions 14 years, 1 month

Stephen J. Turnbull

Julien Danjou writes: > On Fri, Oct 22 2010, Stephen J. Turnbull wrote: > > > What does current-idle-timer do? > > It returns the time since when Emacs is idle, or nil if it's not idle. Good thing I asked; I would have expected it to return the idle-timer currently running (ie, the one that called the function). That's easy. (defun current-idle-timer () ;; or is it `current-idle-time'? "Return XEmacs's idle time in seconds as a float." (itimer-time-difference (current-time) last-command-event-time)) This will never return nil, though. I guess if you really need to know that XEmacs is idle (defvar xemacs-is-idle-p nil) (add-hook 'pre-idle-hook (defun set-xemacs-is-idle-p () (setq xemacs-is-idle-p t))) (add-hook 'pre-command-hook (defun clear-xemacs-is-idle-p () (setq xemacs-is-idle-p nil))) (defun emacs-like-current-idle-timer () (and xemacs-is-idle-p (current-idle-timer))) Of course there may be a race condition here depending on your definition of "idle". However, it wouldn't matter for practical uses (the race window is way less than a second, so if your interval is more than a second, you won't execute anyway if you hit the window, because last-command-event-time will be set and the current-idle-timer function will return a sufficiently small number). > > > run-with-idle-timer is not usable because it only run once by idle > > > session. > > > > ;; probably you want to wrap this up in a macro and use a gensym > > ;; instead of a global symbol > > (defvar timer-foo-timer nil) > > (defun timer-foo () > > (do-foo) > > (when (itimerp timer-foo-timer) (delete-itimer itimer-foo-timer)) > > (setq timer-foo-timer (run-with-idle-timer secs nil #'timer-foo))) > > I don't think this will work. Maybe not. I guess you'd probably need to use a regular timer anyway. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
2 comments

Re: Idle functions 14 years, 1 month

Stephen J. Turnbull

Marcus Harnisch writes: > Well, the Emacs documentation says otherwise: > http://www.gnu.org/s/emacs/manual/html_node/elisp/Idle-Timers.html > > #'current-idle-time (without trailing ?r) returns a rather special > format, a list of three integers. <goggle /> Oh, well, I can't say I'm surprised. XEmacs does have `time-add', `time-subtract', `time-to-seconds', `seconds-to-time', and `input-pending-p', so portable implementations can be written. N.B. XEmacs's `run-with-idle-timer' doesn't accept time values for the idle duration argument (and shouldn't IMO). (Ditto `run-with-timer', but `run-at-time' accepts time values as well as properly formatted strings, and numbers -- which it correctly interprets as seconds-from-now.) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: mark-word (forward and backward) many words???? 14 years, 1 month

Stephen J. Turnbull

Uwe Brauer writes: > >> Regarding Re: mark-word (forward and backward) many words????; "Stephen J. Turnbull" <stephen(a)xemacs.org> adds: > > > > (defun mark-word-backward (&optional count) > > (interactive "p") > > (mark-something 'mark-word-backward > > (lambda (x) > > (and (mark) > > ;; this is tricky: if we get here, then > > ;; mark-something has already done (goto-char (mark)) > > (= (mark) (point)) > > (setq x (- x))) > > (backward-word x)) > > count)) > > Cool, that works, thanks! You're welcome! BTW, I didn't do this at first because your requirements weren't clear to me, and the code is mildly complex because of the direction reversal handling. The key phrase was "I can't predict what repeating the command will mark" which clued me in that the direction reversal handling was important, then a bit of experiment led to the code above (it took about five tries, actually). > Why not include it in the next release of simple.el? Well, I'll think about it. But there are two problems. First, we'd need to do the same for other backward motion commands. More important, it's just not right. The right fix is to make mark-something work as expected with commands whose default direction is backwards. Also, Shift-Control-Left does the right thing by default, so it's not really necessary to make mark-word-backward work by default to get this level of convenience. What bothers me more is that mark-something commands don't mark the whole object, they just mark forward or backward. I guess I'd want an "outward" direction for mark-something, too. This may complicate the issue quite a bit. Posted to the tracker as issue732 (feature request). _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
3 comments

C-S-left (was: mark-word (forward and backward) many words????) 14 years, 1 month

Stephen J. Turnbull

Uwe Brauer writes: > This *does not* work in GNU emacs, I think it will in Emacs 24, though. Or maybe it already does in released Emacsen, but you need to invoke a minor mode. (That feature can be turned off in XEmacs; do C-h a shifted-motion RET to see that various related functions and options.) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Please, somebody look at issue 209 14 years, 1 month

Stephen J. Turnbull

Issue209 "Samba and XEmacs and read-only" has gotten two posts in the last month. Could somebody who groks Windows permission issues *please* take a look at this? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

X11 copy/paste bug 14 years, 1 month

Greg Klanderman

In xemacs 21.4.21, under 'xemacs -q', if you highlight a region with the mouse and then the mouse passes over another frame viewing the same buffer, the highlighted region remains correct but the cut buffer has been corrupted. Greg _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: mark-word (forward and backward) many words???? 14 years, 1 month

Andreas Röhler

Am 22.10.2010 12:17, schrieb Uwe Brauer: > > >>> Regarding Re: mark-word (forward and backward) many words????; Andreas Röhler<andreas.roehler(a)online.de> adds: > > > > Hi Uwe, > > > can't you use mark-word with negative numerical > > argument simply? If not, suggest to sync up with GNU > > version rather than writing extra stuff. > > Yes I can, also in Xemacs. But that means I count the words > I want to mark and then do > say (mark-word -4) > > However when I mark a word with mark-word and then again > execute the function its continues to mark the next word etc > till I am pleased with the result. In order to do this > backward I have to modify mark-something function which does > not look that easy at least after simply running the > debugger I did not understand when the mark is pushed > forward. > > > > Regards > > Uwe > > > Ok, but than push-mark -- CRTL-SPACE -- followed by a forward-/backward-word should do all you need (?) Andreas _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
2 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 October 2010