On Tue, 6 Nov 2012 08:37:56 Egmont Koblinger wrote:
> I looked at the problem a while ago, and figured out that bash's speed
> improved quite a lot during versions, even though the latest is still not
> as fast as it should be, but much better than previous versions. I figured
> out that with bash
On Tue, 6 Nov 2012 08:25:59 Andrew Savchenko wrote:
> On Tue, 6 Nov 2012 07:44:13 +1100 Dmitry Smirnov wrote:
> > On Tue, 6 Nov 2012 04:09:45 Oswald Buddenhagen wrote:
> > > On Sun, Nov 04, 2012 at 11:43:35PM +1100, Dmitry Smirnov wrote:
> > > > What do you think wo
On Tue, 6 Nov 2012 04:09:45 Oswald Buddenhagen wrote:
> On Sun, Nov 04, 2012 at 11:43:35PM +1100, Dmitry Smirnov wrote:
> > What do you think would be the best to do about it?
>
> find out where the slowness *actually* comes from. oprofile, or maybe
> callgrind (once you isolate
Dear Oswald,
On Sun, 4 Nov 2012 21:26:04 Oswald Buddenhagen wrote:
> On Sat, Nov 03, 2012 at 11:34:58AM +1100, Dmitry Smirnov wrote:
> > For example if current working directory is /1/2/3/4/5 and we want to
> > change to /1/2/3/4/5/6 MC sends "cd /1/2/3/4/5/6" to bas
Dear MC team,
This is just an idea of improvement.
At the moment MC is quite ineffectively changing current working
directory (CWD) in subshell mode.
What's happening is MC sends full path of a directory we're we want to
change to the (bash) shell.
For example if current working directory is /1
libreoffice patch is reported as
https://www.midnight-commander.org/ticket/2723
but it looks like there were no progress for whatever reason.
.xz patch was recently accepted for upcoming 4.8.4 (thanks!)
https://www.midnight-commander.org/ticket/2798
as well as support for .gem
https://www.m
