Post by J. ClarkePost by J. ClarkePost by Peter FlassOn Mon, 20 Jul 2020 08:47:44 -0400, Dan Espen
Post by Dan EspenPost by J. ClarkeOn Thu, 25 Jun 2020 20:02:00 -0400, Dan Espen
Post by Dan EspenI've never done it but I believe LibreOffice can be scripted
similar to MS Office.
That's not the problem. You have a GNU APL workspace. You
need to set some parameters in the workspace, start it
running, detect when it has finished, grab some data out of
it, save it to a new location, and if it crashes you have to
recognize that it crashed and log the crash.
It isn't just scripting the office application, it is using
the office application to control another program provided by
a different vendor.
Isn't that what shell scripts are designed for? Use the right
tool for the job.
OK, so tell us how to, from a shell script, display the list of
jobs you can run, quickly select the ones you want, start one
less than the number of cores in the machine of them, monitor
their operation, when one completes start another, display all
of this in the user-friendly interface, and if one crashes
detect that it has crashed and display appropriate messages.
I don't mean to question your requirements or implementation,
I'm sure it took a lot of work to accomplish what you have.
Just curious about some of these things.
lscpu | grep '^CPU(s):'
CPU(s): 4
That's not the problem. The problem is having it keep track of
the number of sessions it has started and that have completed.
Post by Dan EspenI'm not sure what monitoring would entail, but it's pretty easy
to tell if something is running, capture it's PID and use "ps".
Knowing that something is running doesn't help. We know it's
running because we started it. We need to know when it has
completed. APL is an environment, you don't do "APL X" and have
X run. You do APL, then )LOAD X, then Y to start a process,
possibly after setting variables A, B, and C to control that
process, and then it runs until it completes or crashes, then it
sits there either with an error message showing or the cursor
sitting there flashing at you. And once the process is
completed, then we have other steps that need to be performed.
Post by Dan EspenCrashes seem easy to detect and analyze using "abrt".
APL doesn't crash. The program running in APL crashes. APL duly
reports it to the user and remains open. While there are
probably ways to make the interpreter itself crash that would
come under the heading of an "exploit", not something that
happens in normal programming.
Post by Dan EspenThe go to tool for Linux always seems to be a shell script. I
think that's a mistake, sooner or later as the application
grows, shell scripts are going to come up short. Much better to
start out with a real scripting language like Perl or even
better, Python.
Python and Qt (PyQt) can produce some very attractive GUIs.
(Works on Windows too.)
For certain values of "attractive" and it's a lot more work than
displaying the information in an Excel workbook.
And at the time Python was not available to us.
Further, I'm still not sure that I can make Python do what VBA is
doing.
To each his own, or, if the only tool you have is a hammer,
everything looks like a nail,
Well, I think he's working with something pretty complex. I think
they used what they had and now they're in pretty deep. I never
liked being tied to one vendors whims, but sometimes it's hard to
avoid.
In this case, I'd try to keep current on what alternatives I might have.
Our Powers That Be are committed to Microsoft, and at this point
we're damned glad that we were. On Thursday the CEO decreed
"everybody but security, landscaping, and building maintenance will
be working from home starting Monday". So on Monday we were working
from home with damned few hitches, and mostly because the Microsoft
ecosystem has all the tools we needed built into it.
Just chiming in. You don't need MSFT to use a VPN. Some things
actually work better without MSFT.
Who said anything about a VPN? You really should find out what other
people are doing before you tell them how to do it better. In point
of fact our VPN is provided by Cisco.
Well, I'm confused. You talked about working from home. I assumed you
meant the VPN. Aha, I think you were talking about RDP.
X windows is always a network type protocol so all I needed to work
remote was the VPN. At work we were always connecting to other machines
and running stuff there using X Windows.
I had no idea that RDP let you redirect individual windows to another
desktop. RDP stands for "Remote Desktop Protocol'.
I've never used RDP. For a while I had to use Citrix to get get a
windows desktop on a server to do a time sheet. I think RDP did the
same thing at one time.
Okay, just read a bit about RDP. It looks like MSFT added "Seamless
Windows" in 2006:
Seamless Windows: remote applications can run on a client machine that
is served by a Remote Desktop connection.
I just read the Wikipedia page on RDP. That's pretty cool software. It
even includes audio redirection, file sharing and USB redirection.
There are also RDP clients for Linux.
Post by J. ClarkeI saw lots of people using remote desktops to do their work. With X
windows, you don't need to remote the whole desktop, just the
applications you want to run. You do something like "ssh" to your
desktop at work, then start the application you want to use and your
work desktop opens a window on your home machine.
Same with RDP except no SSH needed. But who needs remote desktops?
I think you misunderstood what I meant when I described ssh and then
creating a frame. In fact I created an Emacs window on my home machine
by hitting a single key. Scripts did all the dirty work.
It was pretty cool to connect to my existing edit sessions. More than
once I noticed I hadn't saved my latest changes before leaving work.
Post by J. ClarkeIt can be really cool. At work I might have 5 or 6 files open with
Emacs edits in progress. I go home then ssh, then tell the running
Emacs to create a frame on my home machine. From that "frame" I can
access the same 5 or 6 files as though I never left.
I bring my work computer home. But RDP does that just fine without
being dependent on Emacs. And I don't have to tell the remote machine
to "create a frame".
Emacs just happens to be the tool I was using. I could have been using
any editor or a terminal.
Eventually they forced me to work on a Windows machine so I had a laptop
to take home. i bought a KVM switch so I could continue to use my
mechanical keyboard and large monitor.
--
Dan Espen