Re: ediff-revision drives me nuts - I keep editing the latest revision
17 years, 9 months
Michael Kifer
I don't think this is the right solution.
It is the job of the job of the vc package to make those buffers read-only
(who would want to modify an old version? At least, this should be made
somewhat difficult.)
This is what cvs does, and this is what vc should do as well.
> I use the vc mode stuff with CVS inside XEmacs all the time. I typically
> compare the current file with the latest revision using ediff-revision.
> When you quit it leaves point in the 'a' window. I understand the
> consistency in the various ediff commands all operating that way, but I
> can't tell you how many times I have failed to remember to change buffers
> after a comparision and merrily began editing the file ediff-revision
> checked out of CVS.
>
> I think it would be extremely helpful if ediff-revision always made the 'a'
> buffer read-only to avoid this problem. In fact, if the user asks to
> compare two different versions from the repository, I think both buffers
> should be made read-only.
>
> I modified ediff-vc-internal in my init.el file. This patch seems to do
> what I want:
>
> *** /tmp/skipm/ediff-vers.el Tue Mar 20 15:39:14 2007
> --- /tmp/skipm/init.el Tue Mar 20 15:39:14 2007
> ***************
> *** 11,22 ****
> (save-excursion
> (vc-version-other-window rev1)
> (setq rev1buf (current-buffer)
> ! file1 (buffer-file-name)))
> (save-excursion
> (or (string= rev2 "") ; use current buffer
> (vc-version-other-window rev2))
> (setq rev2buf (current-buffer)
> ! file2 (buffer-file-name)))
> (setq startup-hooks
> (cons `(lambda ()
> (delete-file ,file1)
> --- 11,25 ----
> (save-excursion
> (vc-version-other-window rev1)
> (setq rev1buf (current-buffer)
> ! file1 (buffer-file-name))
> ! (toggle-read-only))
> (save-excursion
> (or (string= rev2 "") ; use current buffer
> (vc-version-other-window rev2))
> (setq rev2buf (current-buffer)
> ! file2 (buffer-file-name))
> ! (and (not (string= rev2 ""))
> ! (toggle-read-only)))
> (setq startup-hooks
> (cons `(lambda ()
> (delete-file ,file1)
>
> --
> Skip Montanaro - skip(a)pobox.com - http://www.webfast.com/~skip/
> "The hippies and the hipsters did some great stuff in the sixties,
> but the geeks pulled their weight too." -- Billy Bragg
>
>
> _______________________________________________
> XEmacs-Beta mailing list
> XEmacs-Beta(a)xemacs.org
> http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
How to get the list of buffers currently displayed in tabs?
17 years, 9 months
Josip Gracin
Hello!
What I'm trying to do is to bind, for example, Super-1 to switch to the
first buffer displayed in the buffer tab list, Super-2 to switch to the
second buffer etc.
It would be easy if (buffers-tab-items) always returned buffers in the
exact same order as they appeared in the tabs. However, the tabs aren't
updated often enough, so the order of displayed tabs does not match the
order that (buffers-tab-items) return.
Is there a way to obtain list of buffers from the tab? I mean, to get
what is really displayed, and not what will be displayed next time that
buffer tabs get refreshed? Or perhaps, is there a way to force a
refresh of buffer tabs in order to synchronize it with what
(buffers-tab-items) returns?
Thanks!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
copy-char-table is buggy
17 years, 9 months
Olivier Galibert
Just a heads up, I'm still working on it. c-c-t has an "interesting"
handling of mirror tables, which does not seem to have much to do with
how they're actually used. Plonking a dirtyfication in the
syntax-related if() "fixes" the old with-syntax-table bug, but the
real fix is to find out what the hell the semantics are supposed to be
and implement them.
Is there an access to mirror tables from lisp? It looks like there
isn't, and that syntax-tables are the only user, but ICBvery easilyW.
OG.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
ediff-revision drives me nuts - I keep editing the latest revision
17 years, 9 months
Skip Montanaro
I use the vc mode stuff with CVS inside XEmacs all the time. I typically
compare the current file with the latest revision using ediff-revision.
When you quit it leaves point in the 'a' window. I understand the
consistency in the various ediff commands all operating that way, but I
can't tell you how many times I have failed to remember to change buffers
after a comparision and merrily began editing the file ediff-revision
checked out of CVS.
I think it would be extremely helpful if ediff-revision always made the 'a'
buffer read-only to avoid this problem. In fact, if the user asks to
compare two different versions from the repository, I think both buffers
should be made read-only.
I modified ediff-vc-internal in my init.el file. This patch seems to do
what I want:
*** /tmp/skipm/ediff-vers.el Tue Mar 20 15:39:14 2007
--- /tmp/skipm/init.el Tue Mar 20 15:39:14 2007
***************
*** 11,22 ****
(save-excursion
(vc-version-other-window rev1)
(setq rev1buf (current-buffer)
! file1 (buffer-file-name)))
(save-excursion
(or (string= rev2 "") ; use current buffer
(vc-version-other-window rev2))
(setq rev2buf (current-buffer)
! file2 (buffer-file-name)))
(setq startup-hooks
(cons `(lambda ()
(delete-file ,file1)
--- 11,25 ----
(save-excursion
(vc-version-other-window rev1)
(setq rev1buf (current-buffer)
! file1 (buffer-file-name))
! (toggle-read-only))
(save-excursion
(or (string= rev2 "") ; use current buffer
(vc-version-other-window rev2))
(setq rev2buf (current-buffer)
! file2 (buffer-file-name))
! (and (not (string= rev2 ""))
! (toggle-read-only)))
(setq startup-hooks
(cons `(lambda ()
(delete-file ,file1)
--
Skip Montanaro - skip(a)pobox.com - http://www.webfast.com/~skip/
"The hippies and the hipsters did some great stuff in the sixties,
but the geeks pulled their weight too." -- Billy Bragg
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
XEmacs Packages have been pre-released (2007-03-22-07)
17 years, 9 months
Norbert Koch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey there everyone.
I have just added the following packages to the 'Pre-Releases'
directory:
New Packages in Pre-Release:
===========================
tramp-1.36-pkg.tar.gz upstream version: 2.0.55
Previously Announced Packages Still in Pre-Release:
==================================================
auctex-1.47-pkg.tar.gz upstream version: 11.55
bbdb-1.32-pkg.tar.gz upstream version: 2.35
calendar-1.31-pkg.tar.gz upstream version: none
docbookide-0.08-pkg.tar.gz upstream version: 0.1
ediff-1.68-pkg.tar.gz upstream version: 2.75
edit-utils-2.37-pkg.tar.gz upstream version: none
gnus-1.91-pkg.tar.gz upstream version: 5.10.8
latin-unity-1.20-pkg.tar.gz upstream version: 1.20
mail-lib-1.79-pkg.tar.gz upstream version: none
misc-games-1.19-pkg.tar.gz upstream version: none
net-utils-1.52-pkg.tar.gz upstream version: N/A
prog-modes-2.10-pkg.tar.gz upstream version: none
riece-1.23-pkg.tar.gz upstream version: 3.1.2
sh-script-1.22-pkg.tar.gz upstream version: 2.0f
viper-1.55-pkg.tar.gz upstream version: 3.09
xemacs-base-2.09-pkg.tar.gz upstream version: none
Detailed Changes:
================
- ------- ChangeLog Entries from xemacs-packages/tramp/ChangeLog -------
2007-03-22 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.36 released.
Installing These:
================
Manually:
- --------
1) Download the packages that you want to install from:
/ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/
2) Unpack them to: [1]
/usr/local/lib/xemacs/xemacs-packages/
3) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.[245].x):
- ----------------------------------------------
1) Tools -> Packages -> Add Download Site -> Pre-Releases
2) Tools -> Packages -> List and Install
3) Select the packages you wish to install (there are brief
instructions at the bottom of the packages buffer).
4) Packages -> Install/Remove Selected
5) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.1.14):
- -------------------------------------------
1) Options -> Manage Packages -> Add Download Site -> Pre-Releases
2) Options -> Manage Packages -> List and Install
3 - 5) As per XEmacs 21.[245].x.
norbert - XEmacs Package Release Manager.
Footnotes:
[1] Note: Mule packages should be installed into:
/usr/local/lib/xemacs/mule-packages/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFGAmPXgu3ywdHdhM0RAkbzAKDLOhZ98q2DckNFphqCovFKeWDvCQCgp41v
GUsyKDZwsC/kkxatvpXth0Y=
=72om
-----END PGP SIGNATURE-----
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
XEmacs Packages have been pre-released (2007-03-22-07)
17 years, 9 months
Norbert Koch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey there everyone.
I have just added the following packages to the 'Pre-Releases'
directory:
New Packages in Pre-Release:
===========================
tramp-1.36-pkg.tar.gz upstream version: 2.0.55
Previously Announced Packages Still in Pre-Release:
==================================================
auctex-1.47-pkg.tar.gz upstream version: 11.55
bbdb-1.32-pkg.tar.gz upstream version: 2.35
calendar-1.31-pkg.tar.gz upstream version: none
docbookide-0.08-pkg.tar.gz upstream version: 0.1
ediff-1.68-pkg.tar.gz upstream version: 2.75
edit-utils-2.37-pkg.tar.gz upstream version: none
gnus-1.91-pkg.tar.gz upstream version: 5.10.8
latin-unity-1.20-pkg.tar.gz upstream version: 1.20
mail-lib-1.79-pkg.tar.gz upstream version: none
misc-games-1.19-pkg.tar.gz upstream version: none
net-utils-1.52-pkg.tar.gz upstream version: N/A
prog-modes-2.10-pkg.tar.gz upstream version: none
riece-1.23-pkg.tar.gz upstream version: 3.1.2
sh-script-1.22-pkg.tar.gz upstream version: 2.0f
viper-1.55-pkg.tar.gz upstream version: 3.09
xemacs-base-2.09-pkg.tar.gz upstream version: none
Detailed Changes:
================
- ------- ChangeLog Entries from xemacs-packages/tramp/ChangeLog -------
2007-03-22 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.36 released.
Installing These:
================
Manually:
- --------
1) Download the packages that you want to install from:
/ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/
2) Unpack them to: [1]
/usr/local/lib/xemacs/xemacs-packages/
3) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.[245].x):
- ----------------------------------------------
1) Tools -> Packages -> Add Download Site -> Pre-Releases
2) Tools -> Packages -> List and Install
3) Select the packages you wish to install (there are brief
instructions at the bottom of the packages buffer).
4) Packages -> Install/Remove Selected
5) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.1.14):
- -------------------------------------------
1) Options -> Manage Packages -> Add Download Site -> Pre-Releases
2) Options -> Manage Packages -> List and Install
3 - 5) As per XEmacs 21.[245].x.
norbert - XEmacs Package Release Manager.
Footnotes:
[1] Note: Mule packages should be installed into:
/usr/local/lib/xemacs/mule-packages/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFGAigmgu3ywdHdhM0RAsuBAKDB2zFE2N8WZUrwlfgk6fgGySV6gwCdFR/1
CIjKBBAlU1O5uSzmwjMgxZI=
=X0ox
-----END PGP SIGNATURE-----
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
[Q] Re: [xemacs-base] Add byte-compiler warning control library
17 years, 9 months
Stephen J. Turnbull
Steve Youngs writes:
> As SXEmacs also has these macros and uses them extensively throughout
> its core lisp, how about adding a form like...
>
> (when (and (fboundp #'with-fboundp)
> (equal (file-name-nondirectory
> (describe-symbol-find-file 'with-fboundp))
> "bytecomp-runtime.elc"))
> (error "bytedecl not loaded: already implemented in your emacs"))
I still don't really like this. AFAICS this makes testing hard.
Having `byte-compile-and-load-file' error because you're using 21.5
doesn't sound like a great idea to me. Sure you can work around it
with fmakunbound, but that's kind of ugly. In general, somebody who
`load's rather than `require's bytedecl probably has a good reason to
do so.
Is there anything wrong with putting `(provide 'bytedecl)' in
lisp/bytecomp-runtime.el? For example, maybe SXEmacs has diverged, in
which case you may not want bytedecl overwriting your macros in older
versions without the provide.
(I'm going to be out of town for a few days, so don't expect further
discussion from me until I get back.)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: [21.5] Check for ar, fix 2.13-ism
17 years, 9 months
Vin Shelton
On 3/13/07, Vin Shelton <acs(a)alumni.princeton.edu> wrote:
> NAG -
> You didn't check in the configure file.
Stephen,
I could check in my version of configure, but it was generated by
autoconf-2.60, not 2.59. Does it matter? What do you want to do?
Thanks,
Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: [Q] Re: [xemacs-base] Add byte-compiler warning control library
17 years, 9 months
Steve Youngs
[ cross-posted and MFT set to xemacs-beta list ]
* Stephen J Turnbull <stephen(a)xemacs.org> writes:
> Steve Youngs writes:
>> but 2 -- package-suppress doesn't seem to work. I just built XEmacs
>> 21.5 CVS HEAD, and I see no evidence that `package-suppress'
>> is doing anything.
> AFAICT what package-suppress is designed to do is to prevent autoloads
> of core libraries from being overwritten by the package version, and
> that's all.
Well, I was under the impression that `package-suppress' would
completely suppress a given library in the packages. With all
attempts to access said library (apart from an explicit `find-file'
maybe) resulting in either the core lisp version if exists or error.
That's why I say `package-suppress' is broken. In a fresh -vanilla
21.5...
(locate-library "regexp-opt")
=> "/usr/local/lib/xemacs/xemacs-packages/lisp/xemacs-base/regexp-opt.elc"
And `find-library', `find-function', `load', `require' all seem to use
the regexp-opt.elc from packages.
> So in a freshly executed XEmacs 21.5, you should see that
> regexp-opt autoloads refer to the core version of regexp-opt.
How do I do that?
> What would you expect to see?
I'd expect to see everything that returns an elisp library to never
return a suppressed one. I'd expect to see everything that loads an
elisp library to never load a suppressed one.
> I guess we'd also want (require 'regexp-opt) to find the core
> version if the package is suppressed?
Definitely.
> I'm not sure that that is correct though; the package version
> should presumably be used when explicitly requiring from another
> package.
That sounds like crazy talk to me. :-)
I'd really like to hear what Ben has to say, seeing as though he was
the one who wrote the suppression stuff.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| SXEmacs - The only _______ you'll ever need. |
| Fill in the blank, yes, it's THAT good! |
|------------------------------------<steve(a)sxemacs.org>---|
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: Changes in font locking
17 years, 9 months
Stephen J. Turnbull
David Kastrup writes:
> people without write access just get ignored, abused or both.
Nonsense, as a quick look at a few XEmacs Beta threads will show.
Quite obviously the bugs themselves and the reporters' demeanor have a
huge amount to do with it, write access or not very little, and very
few reporters receive cross words, and even fewer are ignored.
Ralf dug up the information that I asked for, as well as very useful
information about Emacs that you also chose not to get[1], and he got
the desired result. I greatly appreciate his efforts, because it
turned what I thought would be a hard bug into a pretty superficial
one.[2]
Your bluster, on the other hand, is a lot of sound and fury,
signifying nothing except your frustration. I felt sorry for you,
and more so for the actual users, but as long as I was under the
impression that getting into the guts of copy-syntax-table was
required, to me it wasn't worth the time I estimated it would take.
I have better things to do.
Time constraint and bug triage is just an unfortunate reality in an
open source project staffed by a declining number of volunteers.
Footnotes:
[1] In fact you incorrectly claimed the opposite, which was important
-- it made it seem that the use of copy-syntax-table was a deliberate,
XEmacs-specific change, meaning that the hairy internals probably
would be relevant.
[2] I suspect that `copy-syntax-table' still needs surgery, but that
is pretty clearly not relevant to this particular issue.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta