X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7D6023858004 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1677923776; bh=aFIZFw6zKMvtMZav+3Vul7HkMc1iIo50r7jVe4qwwEE=; h=Date:To:Cc:Subject:In-Reply-To:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=o/SBni2XPSvQauyB1GFsBLEggWfJDopLYoxqydxpbKIprzWSNm0Jxbny6Rn58NUyo RMndfmEemHSWzkNrvz7WH5HI0u3wyXVFQ38AloFI6e+N+z85uHRuSTVOOYwczwTJBR Y71vyTorOhzgpVlT+HwaAVlhhnr6U0qGktmPRYvM= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C97283858D28 Date: Sat, 4 Mar 2023 10:55:53 +0100 To: cygwin AT cygwin DOT com Cc: moss AT cs DOT umass DOT edu Subject: Re: Nano fails to open file "~/.bashrc". Message-ID: <20230304105553.00007dcd@online.de> In-Reply-To: <6a80105e-c0c2-1bad-16a3-b4f1dd38f3b3@cs.umass.edu> References: <0de2dd08-f532-0c21-3685-5fc7e86ef8ee AT gmail DOT com> <165153627 DOT 20230303154721 AT yandex DOT ru> <9abd4f0c-3c51-1626-59d7-f6b65891c99d AT gmail DOT com> <1901530338 DOT 20230303183108 AT yandex DOT ru> <6a80105e-c0c2-1bad-16a3-b4f1dd38f3b3 AT cs DOT umass DOT edu> MIME-Version: 1.0 X-Provags-ID: V03:K1:Fb0C16gMDuOWLNALSZpqaodwlOyAeGNOCCY++Dd9T/0hgzYOLLX rGP/FxUzB+PhJ7o3yfcCfa7y51Ea3x3OXVJR2nacNJaGUfYXuwKhSZJ+fuDf4XV7yaRBX8p tZKZbpMPdH4+5rblCSYbJ4J+Q/KwcGjtB+250ltIDzMaBs6lWpNpYBKrvZa1Ckqupq/izD4 wr4+awO+nVM6oqM1tpmNg== UI-OutboundReport: notjunk:1;M01:P0:rLIIgmD7iMY=;+05P9Qdu0QHWElywZ8oOAskhIl7 qZYVnZ8TUfaxzvXQXLF8Q/ubYJNUfbvFFWoZi7Qx5rEusXJjykoDIN+cqM0ZK3zIqOdRlSa49 1UrGEC2SH+yaMOyrspfqSf1dQxbutdPTQAvJh0wPuHpgHGtnZwiJSDXFqFhMY+gWx55bvuxY2 bMf1SXXjexPmrh02GPn8X1IGlzeFtcfwUFLv3JTuVVpDmEGVVAr1M7BUsDpnQ1Vpoh3gVRn+/ LUApx6oasTrr6AGY2K3QT4Hftvtn/pyjotS01ggxZFYjVhjhVAcLywGUQ8SgJMpqCR8qo1d7H Frln+PpDGmRnd2S5En1Z82x1n2ERYUeRfhmxq78JxDVLaAPgq87EEoo21/0S6M//+2p17ur6G pMNJa+1k0nODM3ubEEN8UqQlPn5N3i6YSKUADzvybnT9fCJg7eciY3rzAHXPr0+zx13+P4i86 FY61+Zaa88CDRNxr1s087YqxuOKrU5eQSeVlJCgK0CLKyFjGgaxdJhqUGfv1/yekazGbsBggT c/CEcA4K5xsYJu7VAb8jGroxZ6LQy9EvWK86sfRG8FuDlje99EGjbp4eNIgvwqP6hv2qdpOlb MNcI4gGaTKJq0SP3NuPp0DCX5Mo3DVweD8x3Bnck8uYWyjDFPIHKhl4XnJysT1Xrz6sJ1onea 9GZUl+G6xQjs4HviA1h3UiSaN2u0Xr5gqLAdPd+q7Q== X-Spam-Status: No, score=1.2 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Oliver Schoede via Cygwin Reply-To: Oliver Schoede Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Fri, 3 Mar 2023 10:53:42 -0500 Eliot Moss via Cygwin wrote: > >- Drop that nano and install the Cygwin one; >- Invoke that nano with a Windows path, perhaps like this: > >nano $(cygpath -wa ~/.bashrc) > Another option is to tinker with your PATH, so that Cygwin's binaries are found before others. I've been doing this in my .profile for years, for similar reasons. It's a hack I admit, don't remember ever running into problems though. Greetings, Oliver -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple