Picon

Re: AUCTeX and emacs on windows

On Wed, Dec 29, 2004 at 12:12:43AM +0100, David Kastrup wrote:
> "Andrej (Andy) Brodnik" <andrej.brodnik <at> imfm.uni-lj.si> writes:
> 
> > Well, let's put it this way, this is not what one, who installed
> > emacs  from  URL  ``http://ftp.gnu.org/gnu/windows/emacs/'' (which  is
> > also suggested  in the INSTALL.windows  directory) wants to  have. The
> > problem is  that if one installs  emacs from the  mentioned site (s)he
> > does not  have cygwin (or mingw)  environment and hence  does not have
> > make suite etc.
> 
> mingw is installed in about 5 minutes.  And probably easier than Emacs
> is installed.

I'm sure not.  For the emacs installation one  only fetches the binary
version,  unpacks (unzips)  it somewhere  and  then makes  a link  (or
whatever is the  name for links under MS-win)  to file run-emacs. This
link ``is'' now the executable -- no compilation, no makes, nothing.

Is the ``make'' part really necessary for the AUCTeX?

LPA

Brian Elmegaard | 29 Dec 09:18
Picon

Re: AUCTeX and emacs on windows

andrej.brodnik <at> imfm.uni-lj.si ("Andrej (Andy) Brodnik") writes:

> Does anybody have any experience with this? 

Sure, it's great.

> I'm not writting about the
> cygwin installation, but straight-forward eamcs instalation.
> 
The windows installer on:
http://www.et.dtu.dk/software/DNA/emacs21.3-setup.exe
includes auctex as well.

The emacs version is not the most recent cvs, but newer than the
official 21.3.

--

-- 
Brian (remove the sport for mail)
http://www.et.dtu.dk/staff/be/be.html

Ralf Angeli | 29 Dec 09:44
Picon

Re: AUCTeX and emacs on windows

* Andrej Brodnik (2004-12-29) writes:

> On Wed, Dec 29, 2004 at 12:12:43AM +0100, David Kastrup wrote:
>> "Andrej (Andy) Brodnik" <andrej.brodnik <at> imfm.uni-lj.si> writes:
>> 
>> > Well, let's put it this way, this is not what one, who installed
>> > emacs  from  URL  ``http://ftp.gnu.org/gnu/windows/emacs/'' (which  is
>> > also suggested  in the INSTALL.windows  directory) wants to  have. The
>> > problem is  that if one installs  emacs from the  mentioned site (s)he
>> > does not  have cygwin (or mingw)  environment and hence  does not have
>> > make suite etc.
>> 
>> mingw is installed in about 5 minutes.  And probably easier than Emacs
>> is installed.
>
> I'm sure not.  For the emacs installation one  only fetches the binary
> version,  unpacks (unzips)  it somewhere  and  then makes  a link  (or
> whatever is the  name for links under MS-win)  to file run-emacs. This
> link ``is'' now the executable -- no compilation, no makes, nothing.

Does `M-x grep-find ...' work after you did this?  What about `M-x
ediff ...'?  Or opening a compressed file with `auto-compression-mode'
enabled?

> Is the ``make'' part really necessary for the AUCTeX?

`make' mainly byte-compiles files.  The interesting part is
`configure'.  This will determine automatically certain values
necessary for AUCTeX functioning properly and do other sanity checks,
so you don't have to.  Of course you could do all this manually but
(Continue reading)

David Kastrup | 29 Dec 10:15
Picon
Picon

Re: AUCTeX and emacs on windows

"Andrej (Andy) Brodnik" <andrej.brodnik <at> imfm.uni-lj.si> writes:

> On Wed, Dec 29, 2004 at 12:12:43AM +0100, David Kastrup wrote:
>> "Andrej (Andy) Brodnik" <andrej.brodnik <at> imfm.uni-lj.si> writes:
>> 
>> > Well, let's put it this way, this is not what one, who installed
>> > emacs  from  URL  ``http://ftp.gnu.org/gnu/windows/emacs/'' (which  is
>> > also suggested  in the INSTALL.windows  directory) wants to  have. The
>> > problem is  that if one installs  emacs from the  mentioned site (s)he
>> > does not  have cygwin (or mingw)  environment and hence  does not have
>> > make suite etc.
>> 
>> mingw is installed in about 5 minutes.  And probably easier than Emacs
>> is installed.
>
> I'm sure not.

You have not tried it then.

> For the emacs installation one only fetches the binary version,
> unpacks (unzips) it somewhere and then makes a link (or whatever is
> the name for links under MS-win) to file run-emacs. This link ``is''
> now the executable -- no compilation, no makes, nothing.

For mingw one fetches the installer, clicks on it and hits a few times
return IIRC.

Please try it out before protesting against it.

--

-- 
(Continue reading)

Nelson H. F. Beebe | 29 Dec 01:51
Picon
Favicon

ReL How to make AUCTEX expand new macros from additional packages?

Discussions today have focused on the presence of doubled slashes
in pathnames from macro expansions, e.g., /var/lib/auctex//emacs-21.

This response comments on standard and historical practice.

Here is what POSIX (IEEE Std 1003.1-2001) has to say:

>> ...
>> 2298 3.266    Pathname
>> 
>> 2299          A character string that is used to identify a file. In the context of IEEE Std 1003.1-2001, a
>> 2300          pathname consists of, at most, {PATH_MAX} bytes, including the terminating null byte. It has an
>> 2301          optional beginning slash, followed by zero or more filenames separated by slashes. A pathname
>> 2302          may optionally contain one or more trailing slashes. Multiple successive slashes are considered
>> 2303          to be the same as one slash.
>> 
>> ....
>> 
>> 3169               A pathname consisting of a single slash shall resolve to the root directory of the process. A null
>> 3170               pathname shall not be successfully resolved. A pathname that begins with two successive
>> 3171               slashes may be interpreted in an implementation-defined manner, although more than two
>> 3172               leading slashes shall be treated as a single slash.
>> ...

Thus, doubled slashes may be significant in POSIX-conformant
filesystems only when they START a pathname.  This may have been
introduced to deal with network-extended filesystems, like the Andrew
File System and the old Apollo Domain filesystem.

Here is what RFC 1808 (Relative Uniform Resource Locators) has to say:
(Continue reading)

David Kastrup | 29 Dec 10:55
Picon
Picon

Re: ReL How to make AUCTEX expand new macros from additional packages?

"Nelson H. F. Beebe" <beebe <at> math.utah.edu> writes:

> Discussions today have focused on the presence of doubled slashes
> in pathnames from macro expansions, e.g., /var/lib/auctex//emacs-21.
>
> This response comments on standard and historical practice.
>
> Here is what POSIX (IEEE Std 1003.1-2001) has to say:

[...]

Last time I looked, nobody claimed that Emacs was a POSIX-compliant
operating system... so we can't demand that it behaves like one.

--

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum


Gmane