May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: is `-name' functional? 26 years, 6 months

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > Hrvoje Niksic <hniksic(a)srce.hr> writes: > > > I would expect `xemacs -name fubar' to start a resourceless XEmacs > > Has this ever worked? I don't recall it ever working. If the > argument given to -name has valid resources they will be used, but > I've never gotten a resourceless XEmacs this way, I've had to use > `xrdb < /dev/null'. I don't know if it ever worked. The funny thing is that I don't even know if it's *supposed* to work. It doesn't work in FSFmacs, for instance. It works for xterm, though. `xterm -name foo' effectively makes xterm ignore all of my resources. If we do agree that this is a bug in need of fixing, maybe someone can produce a patch. It looks easy to fix, but I know next to nothing about X so I wouldn't want to break anything. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- "Memory is like an orgasm. It's a lot better if you don't have to fake it." -- Seymour Cray, on virtual memory

2 participants
1 comments

Re: (Why) Do we still care about Epoch? 26 years, 6 months

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes: > SL Baur <steve(a)xemacs.org> writes: ... >> If the symbol `emacs-major-version' doesn't exist, Emacs cannot load >> the file anyway. > Yes, but it will make the error more obscure, which we should try to > avoid. Just how far back do we need to go? C-h v emacs-major-version `emacs-major-version' is a simple built-in variable. Value: 21 Documentation: Major version number of this version of Emacs, as an integer. Warning: this variable did not exist in Emacs versions earlier than: FSF Emacs: 19.23 XEmacs: 19.10 There was no XEmacs 19.10, 19.10 was the final release of Lucid Emacs. Emacs 19.23 (released May 17, 1994) wasn't considered an official release according to the history section of the internals manual. Lucid Emacs 19.10 was released on May 27, 1994. ... >> The policy has been that etc/NEWS doesn't get rewritten and this is >> in the historical section. Hrvoje, when can we prune the NEWS file >> and put the oldest historical stuff in etc/HISTORY? > Maybe we should create ONEWS, the way FSF does? That would be good.

1 participants
0 comments

Re: is `-name' functional? 26 years, 6 months

Hrvoje Niksic

Martin Buchholz <martin(a)xemacs.org> writes: > Hrvoje> xterm behaves the way I'd expected, and XEmacs behaves > Hrvoje> differently. To reiterate, `xterm -name junk' opens a > Hrvoje> resource-less xterm, and `xemacs -name junk' doesn't appear > Hrvoje> to do anything useful. > > ?? > > ./xemacs -name junk -xrm 'junk.modeline.attributeBackground: yellow' > > gives me a yellow modeline. Martin, what I expected `xemacs -name junk' to do was to get me an XEmacs without any X resources. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- "Beware of bugs in the above code; I have only proved it correct, not tried it." -- Donald Knuth

3 participants
2 comments

packages 26 years, 6 months

Jeff Miller

I added the following ugly hack to get single file packages to load. if we're really looking at a release, this package stuff should get cleaned up a lot more. jeff --- package-get.el.orig Sun May 17 23:45:30 1998 +++ package-get.el Sun May 17 23:49:02 1998 ＠＠ -268,11 +268,11 ＠＠ (error "Package %s does not match md5 checksum" filename))) (message "Retrieved package %s" filename) (sit-for 0) (let ((status - (if (eq (package-get-info-prop this-package 'type) 'single) - (package-admin-add-single-file-package filename - (package-get-staging-dir filename)) +; (if (eq (package-get-info-prop this-package 'type) 'single) +; (package-admin-add-single-file-package filename +; (package-get-staging-dir filename)) (package-admin-add-binary-package - (package-get-staging-dir filename))))) + (package-get-staging-dir filename)))) ;) (when (not (= status 0)) (message "Package failed.") (switch-to-buffer package-admin-temp-buffer)))

1 participants
0 comments

Re: is `-name' functional? 26 years, 6 months

Hrvoje Niksic

Martin Buchholz <martin(a)xemacs.org> writes: > That would be non-standard. > > You still get the Emacs*foo and *foo resources. Just like xterm. Err, no. That's what I'm trying to point out. `xterm -name junk' does *not* read any xterm* resources. > What I do to get a vanilla xemacs with no Martin-specific X resources is: > > xemacs="$1" > shift > unset XFILESEARCHPATH EMACSLOADPATH > exec env \ > XUSERFILESEARCHPATH=$HOME/luser \ > XAPPLRESDIR=$HOME/luser \ > XENVIRONMENT=/dev/null \ > HOME=$HOME/luser \ > "${xemacs}" "$＠" Not something you'd want to tell a user on comp.emacs.xemacs. :-) -- 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: BUG: apropos.el/hyper-apropos.el hate C++ 26 years, 6 months

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes: > SL Baur <steve(a)xemacs.org> writes: >> apropos.el/hyper-apropos.el hate C++[1]. This has never worked >> right, but earlier XEmacsen didn't puke quite this badly. > What do you call "working right"? Rejecting this regexp looks right > to me. Did you mean to write `c\+\+'? I know escaping the plusses works, but it's unintuitive. It's almost certain that two consecutive plusses in that context are being used to hunt for C++ support. If it's going to puke and die anyway, why not filter the regexp through something that escapes two consecutive plusses?

2 participants
1 comments

mail-abbrevs change ? 26 years, 6 months

Jeff Miller

It used to be when I typed in an alias in a vm-mail buffer, then hit the down arrow key, the alias would expand. Now it doesn't expand the alias, though using tab seems to work i see that mail-abbrevs.el was one of the files changes in the latest package updates. was this a deliberate or accidental changes?

1 participants
0 comments

Re: BUG: Suboptimal cUstom capitalization 26 years, 6 months

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > Is there any way to have any control over how custoM capitalizes > buffers? > > Here is an illustration of what I mean: > > Start with xemacs -vanilla, though it doesn't matter, and evaluate the > next two forms in *scratch*. > > (defgroup XEmacs nil > "XEmacs global customizations." > :prefix "xemacs-" > :group 'emacs) Add `:tag "XEmacs"'. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- "Psychos _do not_ explode when sunlight hits them."

1 participants
0 comments

Re: BUG: apropos.el/hyper-apropos.el hate C++ 26 years, 6 months

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > Hrvoje Niksic <hniksic(a)srce.hr> writes: > > > SL Baur <steve(a)xemacs.org> writes: > >> apropos.el/hyper-apropos.el hate C++[1]. This has never worked > >> right, but earlier XEmacsen didn't puke quite this badly. > > > What do you call "working right"? Rejecting this regexp looks right > > to me. Did you mean to write `c\+\+'? > > I know escaping the plusses works, but it's unintuitive. It's > almost certain that two consecutive plusses in that context are > being used to hunt for C++ support. Who said the regexps were intuitive? :-) Seriously, I don't think we should be fixing things that aren't broken. > If it's going to puke and die anyway, why not filter the regexp > through something that escapes two consecutive plusses? Because it would be a relatively obscure hack? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Sauron is alive in Argentina!

1 participants
0 comments

Re: (Why) Do we still care about Epoch? 26 years, 6 months

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > ;;; this file uses opcodes which do not exist in Emacs 19. > > (if (and (boundp 'emacs-version) > (or (and (boundp 'epoch::version) epoch::version) > (string-lessp emacs-version "20"))) > (error "`%s' was compiled for Emacs 20")) > > I propose that this become: > > ;;; this file uses opcodes which do not exist in Emacs 19. > > (or (>= emacs-major-version 20) > (error "`%s' was compiled for Emacs 20")) > > If the symbol `emacs-major-version' doesn't exist, Emacs cannot load > the file anyway. Yes, but it will make the error more obscure, which we should try to avoid. > Ur > > cl-emacs-type > => lucid > > Can we make this print "XEmacs" or "xemacs" instead? It is a symbol internal to the CL package. Someone who wants to actively work on cl*.el should change `cl-emacs-type' to return `xemacs' under XEmacs. > The policy has been that etc/NEWS doesn't get rewritten and this is > in the historical section. Hrvoje, when can we prune the NEWS file > and put the oldest historical stuff in etc/HISTORY? Maybe we should create ONEWS, the way FSF does? -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- If anything goes wrong, blame the random-number generator!

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 May 1998