zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Re: PATCH: sshfs user-side automount
Date: Tue, 17 Mar 2020 14:08:47 +0000	[thread overview]
Message-ID: <1584454127.11232.34.camel@samsung.com> (raw)
In-Reply-To: <20200317140027.361adf36@tarpaulin.shahaf.local2>

On Tue, 2020-03-17 at 14:00 +0000, Daniel Shahaf wrote:
> > > Is the "buflimit" workaround enabled when sshfs(1) is invoked as «sshfs
> > > -o workaround=rename»?  I.e., does defaulting the "rename" workaround
> > > enabled effectively change sshfs(1)'s default behaviour?  
> > My reading of the manual page is you'd need to set "nobuflimit" explicitly
> > to turn it off, else there wouldn't be much use for the "no" prefix,
> > you'd always have to list the ones you want to turn on.  So I think
> > the way it's done is there to fix this exact issue.
> In the alternative semantics, the "no" prefix wouldn't be useless; it'd still
> be useful to allow people to write scripts such as «f() { sshfs -o
> workaround=foo "$@" }» that may be invoked as «f -o workaround=nofoo» to
> disable foo.  However, I agree it's probably implemented as you say.

Yeah, I think that's good enough for our due diligence.  The manual
entry added is explicit about the function's default behaviour and there
is a style you can set.

cheers
pws


      reply	other threads:[~2020-03-17 14:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200217154528eucas1p17c3730dd3979ce40eb383d7f6889c5e2@eucas1p1.samsung.com>
2020-02-17 15:45 ` Peter Stephenson
2020-02-18 10:44   ` Daniel Shahaf
2020-02-18 11:10     ` Peter Stephenson
2020-02-18 11:24       ` Daniel Shahaf
2020-03-16 10:11       ` Peter Stephenson
2020-03-16 18:36         ` Daniel Shahaf
2020-03-17 12:19           ` Peter Stephenson
2020-03-17 14:00             ` Daniel Shahaf
2020-03-17 14:08               ` Peter Stephenson [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1584454127.11232.34.camel@samsung.com \
    --to=p.stephenson@samsung.com \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).