headers
Karl L. | 1 Dec 2004 17:04
Picon
Favicon

Oberon-2 mode

Hi,

I have made an Emacs mode for the programming language Oberon-2 which 
is available at http://home.swipnet.se/karlal/. Is there any interest 
in including an Oberon-2 mode in upcoming Emacs distributions?

Regards,
Karl Landström
Permalink | Reply | 0 comments |
headers
Kevin Rodgers | 1 Dec 2004 17:25
Picon
Favicon

Re: make ffap wildcard-friendly

Dan Jacobson wrote:
> (setq ffap-dired-wildcards "[*?][^/]*\\'") should be the default.
> Hmm, the docstring doesn't say what if then there really is a filename
> with those...

And the comment in the code confirms that is one of the reasons it is
disabled by default:

   ;; Suggestion from RHOGEE, 07 Jul 1994.  Disabled, dired is still
   ;; available by "C-x C-d <pattern>", and valid filenames may
   ;; sometimes contain wildcard characters.

--

-- 
Kevin Rodgers
Permalink | Reply | 1 comment |
headers
Brent S Elmer | 1 Dec 2004 17:52
Picon
Favicon

building emacs 21.3 on powerpc-ibm-aix5.2.0.0


Has anyone had any success building emacs 21.3 on powerpc-ibm-aix5.2.0.0?

Here are my config results:

$ ./configure --prefix=/u3/brente
loading cache ./config.cache
checking host system type... powerpc-ibm-aix5.2.0.0
checking for gcc... (cached) gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking whether ln -s works... (cached) yes
checking how to run the C preprocessor... (cached) gcc -E
checking for a BSD compatible install... /u3/brente/g1/emacs-21.3
/install-sh -c
checking for bison... no
checking for byacc... no
checking for ranlib... (cached) ranlib
checking for AIX... yes
checking the machine- and system-dependent files to find out
 - which libraries the lib-src programs will want, and
 - whether the GNU malloc routines are usable
checking for special C compiler options needed for large files... (cached)
no
checking for _FILE_OFFSET_BITS value needed for large files... (cached) no
checking for _LARGE_FILES value needed for large files... (cached) no
checking for machine/soundcard.h... (cached) no
checking for sys/soundcard.h... (cached) no
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jari Aalto | 1 Dec 2004 19:19
Favicon
Gravatar

Re: find-alternate-file can't handle wildcards

Dan Jacobson <jidanni <at> jidanni.org> writes:

| Make (find-alternate-file "/usr/share/doc/exim4-doc-*") handle wildcards
| just like dired! Currently: File not found and directory write-protected

It's not programmed to do any of that. See C-h f.

    find-alternate-file is an interactive compiled Lisp function in `files'.
    (find-alternate-file FILENAME)

    Find file FILENAME, select its buffer, kill previous buffer.
    If the current buffer now contains an empty file that you just visited
    (presumably by mistake), use this command to visit the file you really want.

C-x C-v is used to replace the _current_ file, not to replace current
file with multiple files.

Jari
Permalink | Reply | 2 comments |
headers
Jari Aalto | 1 Dec 2004 19:17
Favicon
Gravatar

Re: shell-script goofy indentation

Dan Jacobson <jidanni <at> jidanni.org> writes:

| rms> I tried it, and the indentation did not change.  Is that a bug?
| 
| Well shouldn't the then and the else be at the same indentation?
| 
| Wait, more challenges, hit TAB on each line (which shouldn't change
| anything, as I have already hit TAB there)
| if a
|     then b
| elif c
|     then g
| fi

I think the sh-mode is programmed to expect constructs like this:

    if a ; then
        b
    elif c ; then
        g
    fi

Or like this for longish "a" and "c" conditions:

    if a
    then
        b
    elif c
    then
        g
(Continue reading)

Permalink | Reply | 0 comments |
headers
Harald Maier | 1 Dec 2004 19:49
Picon

Re: building emacs 21.3 on powerpc-ibm-aix5.2.0.0

Brent S Elmer <brente <at> us.ibm.com> writes:

> Has anyone had any success building emacs 21.3 on
> powerpc-ibm-aix5.2.0.0?

I build emacs-21.3.50 (development version) under aix-5.2. Not without
problems but it works. In your case it looks that something is
missing (sys/hft.h). Unfortunatley I don't have currently a aix
system :-(. 

Harald
Permalink | Reply | 0 comments |
headers
Stefan Monnier | 1 Dec 2004 20:13
Picon

Re: shell-script goofy indentation

> (setq sh-indent-for-else sh-indent-for-then)

You want (setq sh-indent-for-then 0)
That's what I use anyway, so that I can write

       if foo
       then bar
       else baz
       fi

I always found the default value of sh-indent-for-then (i.e. `+') to be
at best unnatural.

        Stefan
Permalink | Reply | 0 comments |
headers
Juri Linkov | 1 Dec 2004 21:11
Favicon
Gravatar

Re: make ffap wildcard-friendly

Kevin Rodgers <ihs_4664 <at> yahoo.com> writes:
> Dan Jacobson wrote:
>> (setq ffap-dired-wildcards "[*?][^/]*\\'") should be the default.
>> Hmm, the docstring doesn't say what if then there really is a filename
>> with those...
>
> And the comment in the code confirms that is one of the reasons it is
> disabled by default:
>
>    ;; Suggestion from RHOGEE, 07 Jul 1994.  Disabled, dired is still
>    ;; available by "C-x C-d <pattern>", and valid filenames may
>    ;; sometimes contain wildcard characters.

`find-file' can expand wildcards, so it makes sense to call
`find-file' with WILDCARDS argument instead of `dired'.
So I think the following patch will do the right thing:
C-x C-f (find-file-at-point) works like `find-file' wrt wildcards,
and C-x d (dired-at-point) calls `dired' with wildcards.
It contains also fixes to copy correctly all wildcards to the minibuffer.

Index: lisp/ffap.el
===================================================================
RCS file: /cvsroot/emacs/emacs/lisp/ffap.el,v
retrieving revision 1.45
diff -c -r1.45 ffap.el
*** lisp/ffap.el	9 Jun 2004 18:32:06 -0000	1.45
--- lisp/ffap.el	1 Dec 2004 20:02:14 -0000
***************
*** 202,214 ****
  ;; through this section for features that you like, put an appropriate
(Continue reading)

Permalink | Reply | 0 comments |
headers
Juri Linkov | 1 Dec 2004 21:37
Favicon
Gravatar

Re: region sensitive Makefile compile-command

Dan Jacobson <jidanni <at> jidanni.org> writes:
> You guys just got to implement this, so I'm rereqesting it as it is so
> cool.  Make a new variable that we can turn on to enable this:
>
> Here we are in a Makefile,
> a:
>         bla bla
> b:
>         bla bla
>
> Well, if the cursor is anywhere in the a: region, all two lines of it,
> then compile-command should be "make a" (or "make -k a"). If anywhere
> in the b: region, then compile-command should be "make b".
>
> That way when one hits M-x compile, one gets prompted with something
> relevant, not just "make -k" which may not always be what you want.
>
> Currently sadly, one can even put the cursor right on top of the a:
> and normally highly sensitive emacs (especially after enabling ffap)
> still doesn't get the hint.

Good idea.  How about such patch?  However, it doesn't provide
a simple option to turn this off.  I wonder if someone might not like
this behavior?

Index: lisp/progmodes/make-mode.el
===================================================================
RCS file: /cvsroot/emacs/emacs/lisp/progmodes/make-mode.el,v
retrieving revision 1.88
diff -u -r1.88 make-mode.el
(Continue reading)

Permalink | Reply | 2 comments |
headers
Kevin Rodgers | 2 Dec 2004 17:44
Picon
Favicon

Re: ispell file-error "Setting current directory"

Dan Jacobson wrote:
 > rms> Here's how check-ispell-version chooses the directory to use:
 >
 > rms> 	(default-directory (or (and (boundp 'temporary-file-directory)
 > rms> 				    temporary-file-directory)
 > rms> 			       default-directory))
 >
 > rms> Please examine those variables and see what directory it chooses and
 > rms> why.
 >
 > It happened again today.  Had to start a new emacs as replying to mail
 > was blocked by it.  It must be a complex interaction between
 > ispell, gnus, ffap, (and ange-ftp? (which I never use)).
 > In all buffers concerned, the variables you mentioned are $HOME or
 > /tmp, i.e., OK.

That can't be.

 >  All I know is
 > Debugger entered--Lisp error: (file-error "Setting current directory"
 > "no such file or directory" 
"/home/jidanni/http:/www.geocities.com/jidanni/")
 >   call-process("ispell" nil t nil "-vv")
 >   check-ispell-version()

In the *Backtrace* buffer, point should be at the beginning of the
call-process() line.  Move to the check-ispell-version() line, and
please report what these commands display:

e (current-buffer) RET
(Continue reading)

Permalink | Reply | 1 comment |

Gmane