From: Dan Espen <despen@verizon.net>
To: help-gnu-emacs@gnu.org
Subject: Re: run ssh in emacs
Date: Sun, 18 Jan 2015 21:15:04 -0500 [thread overview]
Message-ID: <m9hpaa$88c$1@dont-email.me> (raw)
In-Reply-To: 87oapw2rxq.fsf@bach.histomat.net
Haines Brown <haines@histomat.net> writes:
> Dan Espen <despen@verizon.net> writes:
>
>> Haines Brown <haines@histomat.net> writes:
>>>
>>> I need to do some kind of debug or trace on the command to see just what
>>> is going on, but don't know how to do it.
>>
>> No you don't.
>> You already have the problem staring you in the face.
>>
>> .netrc must have permissions:
>>
>> -r--------
>>
>> It won't work any other way.
>
> Dan, that was the answer! Now I understand the reason for the
> permissions warning message. One would think man netrc would mention
> this restriction.
From "man netrc":
ftp will abort the auto-login process if the .netrc is readable by
anyone besides the user.
> A primitive -r-------- strikes me as a nuisance because I would have to
> go through chmod just to modify the file, but I find that ange-ftp
> also works with -rw-------.
Open the file with Emacs.
Just find the file as normal.
To change from read-only type ^x^q.
Make your changes.
Emacs will ask if it's okay when you save the file.
--
Dan Espen
next prev parent reply other threads:[~2015-01-19 2:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 19:32 run ssh in emacs Haines Brown
2015-01-12 19:42 ` Tory S. Anderson
2015-01-13 12:38 ` Haines Brown
2015-01-13 13:04 ` Nikolay Kudryavtsev
2015-01-13 13:18 ` Tory S. Anderson
2015-01-13 13:21 ` Michael Albinus
2015-01-13 13:18 ` Tory S. Anderson
2015-01-13 13:28 ` Michael Albinus
2015-01-13 14:29 ` Tory S. Anderson
2015-01-13 15:16 ` Haines Brown
2015-01-13 15:23 ` Tory S. Anderson
2015-01-13 18:11 ` Haines Brown
2015-01-14 4:26 ` Bob Proulx
[not found] ` <mailman.17817.1421162618.1147.help-gnu-emacs@gnu.org>
2015-01-15 16:26 ` Haines Brown
2015-01-15 17:19 ` Ted Zlatanov
2015-01-15 20:26 ` Haines Brown
2015-01-15 21:10 ` Ted Zlatanov
2015-01-16 17:18 ` Haines Brown
2015-01-16 19:59 ` Michael Albinus
[not found] ` <mailman.18043.1421438398.1147.help-gnu-emacs@gnu.org>
2015-01-16 20:55 ` Haines Brown
2015-01-16 21:34 ` Dan Espen
2015-01-16 21:36 ` Michael Albinus
2015-01-17 12:17 ` Haines Brown
2015-01-17 17:12 ` Michael Albinus
[not found] ` <mailman.18073.1421514787.1147.help-gnu-emacs@gnu.org>
2015-01-17 20:15 ` Haines Brown
2015-01-17 23:32 ` Dan Espen
2015-01-18 12:29 ` Haines Brown
2015-01-19 2:15 ` Dan Espen [this message]
[not found] ` <mailman.18064.1421497097.1147.help-gnu-emacs@gnu.org>
2015-01-17 14:13 ` Dan Espen
[not found] ` <mailman.17814.1421162216.1147.help-gnu-emacs@gnu.org>
2015-01-13 16:59 ` Dan Espen
[not found] ` <mailman.17800.1421154285.1147.help-gnu-emacs@gnu.org>
2015-01-14 12:14 ` Haines Brown
2015-01-14 19:55 ` Bob Proulx
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='m9hpaa$88c$1@dont-email.me' \
--to=despen@verizon.net \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).