tramp-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tramp-announce for alerts of new versions only


From: Michael Albinus
Subject: Re: tramp-announce for alerts of new versions only
Date: Wed, 20 Nov 2019 19:40:59 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)

積丹尼 Dan Jacobson <address@hidden> writes:

Hi Dan,

> (info "(tramp) Top") says
>    There is a mailing list for TRAMP, available at
>    <address@hidden>, and archived at the TRAMP Mail Archive
>    (https://lists.gnu.org/r/tramp-devel/).
> OK but maybe there should also be a tramp-announce list,
> else how does one subscribe to just alerts about new versions?

Tramp is released as ELPA package. You see all ELPA announcements at the
<address@hidden> mailing list.

> P.S., maybe there should also be a github/.../issues place, for users to
> post minor bug reports, instead of sending them to all subscribers of
> tramp-devel. (GitHub seems to work real good, vs. other cranky old bug 
> trackers.)

No way. I don't use github, I even have no github account.

> P.S.S., on (info "(tramp) Basic Installation")
>
>    • Choose a directory, say ‘~/emacs/’.  Change into that directory and
>      unpack the tarball.  This will give you a directory
>      ‘~/emacs/tramp-2.4.2/’ which contains subdirectories ‘lisp’ for the
>      Lisp code, ‘texi’ for the documentation, and ‘test’ for code
>      running TRAMP’s test suite.  Make a symbolic link:
>
>           $ ln -s tramp-2.4.2 tramp
>
> OK but mention if you used git to download, then no link is needed.

If you use git, there's even no tarball to unpack :-)

>    • ‘cd’ to ‘~/emacs/tramp/’.  If you’ve taken TRAMP from the GIT
>      sources, type ‘autoconf’ in order to get an up-to-date ‘configure’
>      script.
>
> OK but mention if this is a first time git clone (?), then you don't even
> need autoconf on your system.

You will still need autoconf, if configure.ac or aclocal.m4 is
changed. But you're right, you don't need to enter this manually, again.

Changed in the text.

>    • You can remove the byte-compiled Lisp files and the Info manual
>      from the source directory by typing ‘make clean’.  To also remove
>      the files that ‘configure’ created, type ‘make distclean’.
>
> OK but mention if you mean to type distclean "instead", or "also afterwards".

Applied.

>    • NOTE: If you run into problems running the example ‘make’ command,
>      don’t despair.  You can still byte compile the ‘*.el’ files by
>      opening Emacs in ‘dired’ (‘C-x d’) mode, at ‘~/emacs/tramp/lisp’.
>      Mark the lisp files with ‘m’, then press ‘B’ to byte compile your
>      selections.
>
> Change:
> <    Something similar can be done to create                       the info 
> manual.  Just
>>    Something similar can be done if there were problems creating the info 
>> manual.  Just
>      change to directory ‘~/emacs/tramp/texi’ and load the ‘tramp.texi’
>      file in Emacs.  Then press ‘M-x texinfo-format-buffer <RET>’ to
>      generate ‘~/emacs/tramp/info/tramp’.

Applied.

Thanks for the review!

Best regards, Michael.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]