extra blanks in the *Marked Files* buffer of dired

Gentlemen, I have detected extra blanks in the *Marked Files* buffer
of dired!: 
$ emacs -nw
C-x d RET m m ! C-x o C-x o C-e
--

-- 
http://jidanni.org/ Taiwan(04)25854780

Re: M-x compile does not set the EMACS env var anymore

This has been fixed for 21.3, the coming bug-fix release.

["Jeff Sheinberg" <jeff <at> bsrd.net>] re: emacs doesn't restore one's non X windows prompt

Fellas, he has a fix.
If this is a terminfo description bug too, then somebody please report it.

I have a fix for this problem,

    Gentlemen, in good old tty mode, outside of X windows,
    I have in .bashrc
    if test $DISPLAY$EMACS; then :; else
        #VGA-softcursor.txt says to get red non-blinking block prompt
        echo -e '\033[?17;0;64c'
    fi

One must create an edited terminfo entry, so run the attached
Makefile from your ~/.terminfo directory,

I didn't reply on Usenet because I am not yet setup to do so.

HTH,
--

-- 

Makefile mode comment color didn't notice backslash continuation

Gentlenerds, Makefile mode has blown it by making comment_B appear in
command color when in fact it is a comment just like comment_A:
$ cat Makefile
a:
	echo hello # comment_A \
	comment_B
I bet it was thinking 'shell script'.
--

-- 
http://jidanni.org/ Taiwan(04)25854780

it supposes I want to see a man page with a slash in its name

/ e t c / t u r d l y ESC x m a n RET
and it prompts me with the default suggestion of a man page with
slashes in its name.  Why can't it prompt me with the default just
"turdly"?  How are you going to pass ISO-9002 with stuff like this?
--

-- 
http://jidanni.org/ Taiwan(04)25854780

query-replace conflicts with mouse operation

Hi,

query-replace generates undesired results if copy/paste is done while 
entering FROM-STRING. To reproduce:

- load a file which contains a string several times
- start a query-replace (M-%)
- copy one of <string> ocurrences with mouse-1 drag
- paste it as FROM-STRING with mouse-2 and press return
- enter any TO-STRING and press return

=> emacs will reply "Replaced 0 occurrences" or "The mark is not set now, so there is no region"!

Which does imho not make sense and is very confusing for mouse-oriented users. 

The behaviour will vary depending on if there was a region before.

I investigated the problem a bit and guess...:

- If a region is defined before starting a query-replace, the replace is
  restricted to the region (which is probably intentional). 
- The problem seems to arise, because the replace does not use the region like 
  it is defined before the query-replace call, but the region that is generated
  by the copy operation. 

I have seen this both in version 21.2 and the current cvs release.

Thanks,
Ulf

MacOS X build problem

I grabbed emacs from subversions.gnu.org as directed on
http://members.shaw.ca/akochoi-emacs/ last night and tried to build it
on my iBook, which is running Jaguar.  After getting through the whole
build process and running make install, I get the following error:

pi% /usr/local/bin/emacs
Fatal error (6).zsh: abort      /usr/local/bin/emacs

Obviously this isn't very helpful at all for debugging purposes.  What
information should I supply so the bug can be fixed?

Chris

Re: MacOS X build problem

On 1 Feb 2003, Chris Tessone wrote:

> pi% /usr/local/bin/emacs
> Fatal error (6).zsh: abort      /usr/local/bin/emacs
> 
> Obviously this isn't very helpful at all for debugging purposes.  What
> information should I supply so the bug can be fixed?

See the section "Reporting Bugs" in the Emacs manual and the file 
etc/DEBUG in the distribution.

Thanks!

Re: MacOS X build problem

Hi Chris,

Chris Tessone <tessone <at> polyglut.net> writes:
> pi% /usr/local/bin/emacs
> Fatal error (6).zsh: abort      /usr/local/bin/emacs

You can either run "emacs -nw" or you run Emacs from the Emacs.app
application.  You can not run the Aqua windowing interface from
/usr/local/bin.

And yes, a better error message is missing and a bug report about that
is a good idea.

Hope this helps, benny

Re: debug-on-call

Dan Jacobson wrote:

> I wanted to have emacs stop if it ever called a function, but no:
> debug-on-entry: Function base64-encode-region is a primitive
> 
> I don't need to debug inside that function. All I wanted was to see a
> backtrace so I can tell the layers of stuff calling that function.

(defadvice base64-encode-region (before debug activate)
   "Debug (when called from an Emacs Lisp function)."
   (debug))

--

-- 
<a href="mailto:&lt;kevin.rodgers&#64;ihs.com&gt;">Kevin Rodgers</a>