Re: Personality settings in Eudora
Re: Personality settings in Eudora
- Subject: Re: Personality settings in Eudora
- From: Doug McNutt <email@hidden>
- Date: Tue, 15 Apr 2003 11:29:46 -0600
At 01:58 +0100 4/15/03, John Delacour wrote:
>
You're making far too much of a meal of it.
Well. I guess I wasn't as precise as I should have been. I do need to have the running copy of Eudora continue to do the things it is set up for. After the timed remote request regularly scheduled reads need to happen as programmed in the original settings. What I really want is equivalent to selecting "Admin" in the personalities window and poking the button that checks mail for the selected personality. This bit of drivel works not. All personalities get checked immediately.
tell application "Eudora"
tell personality "Admin"
connect with checking and waiting without sending
end tell
end tell
John continued:
>
You have observed:
>
<x-eudora-setting:38> When checked, nothing interesting will happen.
>
That means just what is says, so leave it at the default "n" because nothing interesting will happen even if you set it to "BANG!"
I really thought, perhaps wishfully, that checking mail was something "interesting" and while I am mucking with temporary settings I really don't want them being interpreted in some other thread. I now think that the proper meaning of setting 38 is "When checked I won't even look at it. Leave it alone dammit." but I'm really not so sure. Setting 84 seems to be the right one to use.
>
<x-eudora-setting:6> How often (in minutes) Eudora will check for mail.
>
set setting 6 to "" -- or some very big number
>
<x-eudora-setting:153> When checked, Eudora will check for mail at the specified interval.
>
set setting 153 to "" -- but it makes no difference if setting 6 is ""
And that's the suggestion that provides the fix. Thank you John. By forgetting about setting 153 which is the box that enables periodic connections one can avoid the apparent trigger that forces connection whenever it changes from off to on like an edge triggered flip-flop. Setting the time interval to infinity on a temporary basis has the same effect without the trigger. (Caveat. I can't see the source code so all I have is experimental results.)
Here is a working version:
tell application "Eudora"
activate -- to see activity, remove me someday
set setting 84 to "y" -- turn off scheduled connects
set plist to {}
set qlist to {}
set pcount to count of personalities
repeat with jill from 1 to pcount -- saving existing settings
set plist to plist & setting 183 of personality jill
set qlist to qlist & setting 6 of personality jill -- was 153
set setting 183 of personality jill to "y" -- means no
set setting 6 of personality jill to "" -- infinity
end repeat
set setting 183 of personality "Admin" to "n" -- means yes
set setting 84 to "n" -- allow connections
connect with checking and waiting without sending
-- Only account Admin gets read as expected.
set setting 84 to "y" -- turn all connects off once again
repeat with jill from 1 to pcount
-- reset all of the original options.
set setting 183 of personality jill to item jill of plist
set setting 6 of personality jill to item jill of qlist
end repeat
set setting 84 to "n" -- turn scheduled connects back on
end tell
One more observation: John said:
>
You have observed:
>
<x-eudora-setting:84> When checked, Eudora will make no connections.
>
That means just what is says, so leave it at "" or "n" or else you won't be able to make ANY connexions.
It appears that setting 84 can be set on a personality basis.
tell application "Eudora"
set plist to {} as list
set setting 84 of personality "Admin" to "y"
set setting 84 of personality "dmcnutt" to "n"
set plist to setting 84 of personality "Admin"
get setting 84 of personality "dmcnutt"
set plist to plist & result
end tell
plist -- result window shows "yn" (Why not {"y", "n"} ) ?????
Note that "Admin" and "dmcnutt" do acquire separate settings for 84. It's possible that a connect with all but one personality having 84 set to quiet would accomplish what I want without mucking with any other settings. Someday I shall experiment some more. Documentation from Qualcomm - naahhh. Did someone say you have to be a masochist to script Eudora?
An AppleScript note:
I have to "get the setting" and then do a "set plist to plist & result" above. AppleScript returns an error otherwise and I wonder why. I also wonder why the concatenation is not performed in list context as it clearly is in the longer script. (Should I have called it @plist?)
So now all I have to do is figure out how to :
tell application "Eudora" of machine "Jupiter"
run script CheckAdmin
end tell
Maybe if I say please?
--
Applescript syntax is like English spelling:
Roughly, but not thoroughly, thought through.
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.