>> While Far just works as is.
> 
> but just on a single platform ;)

Yes unfortunately, but at least now it has UNICODE 
support plus x64 support. Looking at the code, it will 
never be ported to other OS though.

I was also trying it with WINE, but the results 
are very inconsistent.

>> Storing settings in .ini (or .xml) files as opposed to
>> registry. Author Eugene Roshal insisted on registry
>> (while I insisted that this is a mistake - this was in
>> 1996), so finally some .bat files have born to save/restore
>> reg content, but I miss "portability" to this very date,
>> at least as an option. F.e. I store Far executables on
>> a VMWare virtual disk (or network share, or host drive),
>> and access it from multiple VMs. Now keeping in sync my
>> Far preferences between VMs is practically impossible.
>> 
>> If you agree, you could ask for this feature on russian
>> Far Manager forums :)
> 
> Do you mean they ignore English messages? ;)

No, but certainly Russian section looked more active :)
(most ChangeLogs/comments and docs are still produced 
in Russian)

Maybe I'll do it later, but given the 5% success rate of 
my reports I'll have to catch some more optimistic 
mood to care enough to create a post and argue about a 
feature. Until then I'm trying to detach myself from Far 
some more.

> I am not such a power user of Far as you, I don't have any favorite
> configuration sets that I would want to preserve across prophylactic
> Windows reinstalls. And if I did, the bat files work. Well, years ago
> when I was a primarily Windows user, this Far behaviour irritated me,
> (the only settings i wanted to save were sane archiver command lines
> instead of the ones supplied with Far) but now I use Windows only
> episodically.

Yes, and how lazy I am, I still didn't import those archiver 
settings from my old PC. Probably that's how old customs die, 
in this case I switched to unzip on cmdline, or I use 
OS X for such purpose.

>> Thank you. I figured these two, now I have to get used to
>> them. But I'll for sure miss things like Alt+<+>, <Gray+>
>> and <Shift+Cursor> to make selections in a more sophisticated
>> way.
> 
> + and - when typed on an empty command line start the select mask dialog.

Thanks, it even works here on OS X.

[ but why PgUp/PgDn doesn't, it escapes me, I've even 
thought it the keys, but it scrolls the whole terminal 
buffer instead. ]

> As for Shift-Cursor, it's not A True NC-Way ;) I guess it initially
> appeared in GUI-based NC clones like Windows Commander.

That's the one I use most seldom, so I can do without :)

> Alt+<+> is indeed an interesting feature if you mean "select all files
> with the same name and different extension". But I usually switch to

Same extension with different name, but yes, it is what you say.

> sorting by name for such operations, it's also safer when you see
> files you are selecting. Of course if there are tens of such files
> it's faster to type rm filemask.* ENTER, or if you prefer
> CUI, type + filemask.* ENTER F8 ENTER.

Hm, can be done, but so much slower.

> Although I don't need these two features, I suppose that if someone
> would create corresponding tickets on midnight-commander.com, they'll
> be reviewed in a short period of time. Even without patches attached.
> I'd rather support a feature that would add support for M-Enter and %
> macros in the group select dialog.

That's also nice.

Maybe I'll create such ticket in the future, as for now, on 
OS X latest GIT trunk doesn't build at all (there is no 
'configure' file and 'autoconf' just errors), so I'll try 
on Linux instead.

Brgds,
Viktor

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to