Sorting the global dir history

[vefatica]

Steve (or anyone else interested) ...

I started a new thread because it would have been too difficult to find the earlier discussion of this.

You might want to check out ftp://lucky.syr.edu/4plugins/dirsort.zip.

It contains DIRSORT.EXE (syntax: DIRSORT [/R(everse)]) which will sort the global directory history list (and make all the drive letters uppercase because I find that easier to read).

I also have DIRSORT in a test version of the 4UTILS plugin but I'm hesitant to leave it there without some indication that folks will find it useful. So I'd appreciate feedback.

Rex, having all the drive letters in the same case is nice on the eyes. I imagine it would be a one-liner for you to do that when a directory is added to the list. Would you consider it?

 

[rconn]

Steve (or anyone else interested) ...

Rex, having all the drive letters in the same case is nice on the eyes. I imagine it would be a one-liner for you to do that when a directory is added to the list. Would you consider it?

No - it would break some third-party apps (like ClearCase).

 

[vefatica]

No - it would break some third-party apps (like ClearCase).

No big deal but I'd really like to understand what you mean. How can capitalizing the drive letter of a case-insensitive path in a window shown by TCC break anything?

 

[rconn]

vefatica wrote:

> ---Quote (Originally by rconn)---
> No - it would break some third-party apps (like ClearCase).
> ---End Quote---
> No big deal but I'd really like to understand what you mean. How can capitalizing the drive letter of a case-insensitive path in a window shown by TCC break anything?

Some apps ported over from Linux/Unix (like ClearCase) ARE
case-sensitive. (At one time 4NT *did* capitalize the drive letter, and
it caused a surprising number of problems.)

Rex Conn
JP Software

 

[vefatica]

Some apps ported over from Linux/Unix (like ClearCase) ARE
case-sensitive. (At one time 4NT *did* capitalize the drive letter, and
it caused a surprising number of problems.)

In this thread, I did not receive mail notification of my original post (of last night) or your most recent reply (now two hours after it). Is there no fixing this thing?

 

[Steve Fabian]

You might want to check out ftp://lucky.syr.edu/4plugins/dirsort.zip.

It contains DIRSORT.EXE (syntax: DIRSORT [/R(everse)]) which will sort the global directory history list (and make all the drive letters uppercase because I find that easier to read).

I also have DIRSORT in a test version of the 4UTILS plugin but I'm hesitant to leave it there without some indication that folks will find it useful. So I'd appreciate feedback.

Possibly a separate plug-in (4SORT) that can sort not only the directory history, but any one of the global tables. When sorting functions or aliases, it should use only the function or alias name as sort key. Command history sorting would be most useful if left parentheses and spaces preceding commands were ignored.

How do you ever get lower case drive letters into your directory history?

 

[vefatica]

On Thu, 22 Jan 2009 10:44:18 -0600, Steve Fábián <> wrote:

>Possibly a separate plug-in (4SORT) that can sort not only the directory history, but any one of the global tables. When sorting functions or aliases, it should use only the function or alias name as sort key. Command history sorting would be most useful if left parentheses and spaces preceding commands were ignored.
>
>How do you ever get lower case drive letters into your directory history?

I don't know how they get in there but they do.

I am still not convinced there's any good reason to sort the command history.
Recent commands would no longer be recent; consecutive commands might no longer
be consecutive. I'd post the plugin code for DIRSORT if anyone wants to
elaborate on it or do similar things with the other lists.

One change that would help you (maybe Rex would consider it) is to do a wildcard
search on a partially-specified command line rather than trying to exactly match
the initial part (as I think it does now). For example, you enter "*for*type"
and invoke the command history and the history mechanism uses "*for*type*" (note
added "*") as a wildcard search criterion, finding, for example, "(for %f in
(*.txt) type %f) >> bigfile".

 

[rconn]

In this thread, I did not receive mail notification of my original post (of last night) or your most recent reply (now two hours after it). Is there no fixing this thing?

If you know of a way to convince the Chinese to stop sending several million emails per day to our mail server, that would help. (They're not getting through, but they're making it nearly impossible to do anything else.)

On a somewhat related note, I did fix the issue with the email headers last week, but despite the dozens of complaints I had received earlier, nobody actually seems to have noticed (or cared?) that it's working now.

 

[Jim Cook]

>
>
> On a somewhat related note, I did fix the issue with the email headers last
> week, but despite the dozens of complaints I had received earlier, nobody
> actually seems to have noticed (or cared?) that it's working now.
>
>

Hey! I'd stopped paying attention to the headers at all because they were
useless and annoying.

Thank you, thank you, thank you!!

--
Jim Cook
2009 Saturdays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Sunday.

 

[Steve Fabian]

rconn wrote:
| ---Quote (Originally by vefatica)---
| In this thread, I did not receive mail notification of my original
| post (of last night) or your most recent reply (now two hours after
| it). Is there no fixing this thing? ---End Quote---
|
| If you know of a way to convince the Chinese to stop sending several
| million emails per day to our mail server, that would help. (They're
| not getting through, but they're making it nearly impossible to do
| anything else.)

Is "@jpsoft.com" under attack, or the mail server in general?

| On a somewhat related note, I did fix the issue with the email
| headers last week, but despite the dozens of complaints I had
| received earlier, nobody actually seems to have noticed (or cared?)
| that it's working now.

I did notice with appreciation, but with so many other problems (esp. the
loss of V10 installability) I did not have a chance to send a KUDO.
--
Steve

 

[vefatica]

On Thu, 22 Jan 2009 12:00:35 -0600, rconn <> wrote:

>---Quote (Originally by vefatica)---
>In this thread, I did not receive mail notification of my original post (of last night) or your most recent reply (now two hours after it). Is there no fixing this thing?
>---End Quote---
>
>If you know of a way to convince the Chinese to stop sending several million emails per day to our mail server, that would help. (They're not getting through, but they're making it nearly impossible to do anything else.)

I don't know how they're handling it but I wish something similar would happen
to the mail server I administer so I could see how effective IPSEC would be. I'd
use IPSEC (Unix should have it) to have the OS block specific IPs or vast
subnets. The mail server would never see them. But I don't know how effective
that would be against such a large number of connections.

>On a somewhat related note, I did fix the issue with the email headers last week, but despite the dozens of complaints I had received earlier, nobody actually seems to have noticed (or cared?) that it's working now.

I wouldn't have noticed it because quite a while ago I wrote and implemented an
extension ("policy") fo my mail server that turned the offending "From:" header
into a "X-om:" header.

 

[rconn]

rconn wrote:
| If you know of a way to convince the Chinese to stop sending several
| million emails per day to our mail server, that would help. (They're
| not getting through, but they're making it nearly impossible to do
| anything else.)

Is "@jpsoft.com" under attack, or the mail server in general?

Just the jpsoft.com mail server; the web site is only suffering incidental damage from the overload.

 

[Steve Fabian]

rconn wrote:
| ---Quote (Originally by Steve Fábián)---
| rconn wrote:
|| If you know of a way to convince the Chinese to stop sending several
|| million emails per day to our mail server, that would help. (They're
|| not getting through, but they're making it nearly impossible to do
|| anything else.)
|
| Is "@jpsoft.com" under attack, or the mail server in general?
| ---End Quote---
|
| Just the jpsoft.com mail server; the web site is only suffering
| incidental damage from the overload.

Sorry, what I meant to ask was: is all that spam directed to the jpsoft.com
domain, or against multiple domains served by the same mail server? I think
you meant the former, and you implied that the same computer is the server
for the jpsoft.com website.
--
Steve

 

[rconn]

Steve Fábián wrote:

> Sorry, what I meant to ask was: is all that spam directed to the jpsoft.com
> domain, or against multiple domains served by the same mail server? I think
> you meant the former, and you implied that the same computer is the server
> for the jpsoft.com website.

It's all directed at the jpsoft.com domain.

Rex Conn
JP Software