From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Cc: Brian Inglis <Brian.Inglis@shaw.ca>
Subject: Re: MC bug (to Marco Atzeri)
Date: Wed, 15 Mar 2023 17:59:53 +0100 [thread overview]
Message-ID: <CAB8Xom8nQKefBJUZA3a4mmZHtv1RyGTCVQ8-Nf4nkTRyVOfsfQ@mail.gmail.com> (raw)
In-Reply-To: <8ad33f1e-9617-f328-ea75-0cd19cce55c8@Shaw.ca>
On Wed, Mar 15, 2023 at 4:24 PM Brian Inglis via Cygwin
<cygwin@cygwin.com> wrote:
>
> On 2023-03-15 09:10, Dan Pejchar via Cygwin wrote:
Hi Dan,
> > I am a linux user but I have to use windows sometimes and I would love to
> > use the midnight commander in my terminal, but there is a bug which doesn't
> > really allow me to use it. I am using it on Windows 10 and when I change
> > the directory in the mc, it only changes in the mc window, but when I press
> > CTRL+O it stays in the same directory. And when I press CTRL+O it doesn't
> > return to the previously opened directory. I will do a steps to reproduce
> > list below. Also it is sometimes very slow when changing directories.
> ...
> > Just for clarity, I am talking about this package
> > https://www.cygwin.com/packages/summary/mc.html .
Noted, but my personal PC is dead and I need to travel for work,
so do not expect an investigation/solution short term.
> Have you tried installing xinit to run Cygwin/X and use pcmanfm?
> Only slow with directories containing thousands of files.
> Just don't stay in directories after other processes delete them - e.g. builds:
> when pcmanfm notices, it dies!
Hi Brian
the Cygwin version is a console only application
Regards
Marco
prev parent reply other threads:[~2023-03-15 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 15:10 Dan Pejchar
2023-03-15 15:23 ` Brian Inglis
2023-03-15 16:59 ` marco atzeri [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=CAB8Xom8nQKefBJUZA3a4mmZHtv1RyGTCVQ8-Nf4nkTRyVOfsfQ@mail.gmail.com \
--to=marco.atzeri@gmail.com \
--cc=Brian.Inglis@shaw.ca \
--cc=cygwin@cygwin.com \
/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).