EZ as a Word Processor
If you work for a few minutes without saving, ez will automatically save for you. You can tell this is happening when the message line at the bottom suddenly shows “Checkpointing...” and then “Checkpointed”. The file is written to a separate file named like the original filename except “.CKP” is appended. Thus if you edit test.d, the checkpoint file will be test.d.CKP. When you use the “Save” command, your original file is replaced with the new version and the checkpoint file is removed.
It is important to understand that the word processing files created by ez have their own distinctive format, just like your favorite commercial word processors. This format was conveniently designed from the start to allow ez documents to be sent via conventional electronic mail systems.
This format is the “magic” that allows ez to be so simple. The data quite literally defines what can be done to it. As the data is read, programs that match the data are automatically loaded for you. ez is not a single program, but a group of programs that can cooperate with each other, each of which knows how to manipulate a certain type of object. If ez reads a document with text in it, the text-editing program edits the text object. If ez reads a document with a bitmap (picture), the bitmap-editing program edits the bitmap object. If your document has several different objects, all the different programs cooperate to edit the objects.
However, you need to do more than edit your documents. You need to print them and send them to other people, both electronically and on paper. Therefore, filters have been written to convert AUIS documents to several different formats. To print your documents, you can convert them to PostScript. To exchange documents with people running other word processing systems, you can convert them to RTF format, the most common document interchange format. You can even convert your documents to straight ASCII, though of course all your fonts and pictures will be lost.
One of the simplest things you can do with ez is to add styles to a document. Styles appear as menu items. If you look at the menus, you will find quite a few styles can be chosen. In Figure 1 you can see some of the more common styles—italics, bold, centered, or left/right justified, and various font sizes to name a few.
Most styles can co-exist peacefully—italics and bold make bold-italics. Others cancel each other out—like center and right-justify text. Some styles you can apply more than once—changing font sizes can be done by successive applications of bigger. To remove a style, select and area and chose the Plainer (F7) menu item. To remove all styles, choose the Plainest (F8) menu item. You can see what styles have been applied by placing the cursor at some point in your document and then entering “Esc-s” (press the escape key and then press the “s” key). In the message area at the bottom of the screen you will see a description of the styles that apply at that point.
In Figure 1 you can see our document has two types of data—conventional text and a small picture. Tech-nically each of these are insets to ez. An inset is just a piece of data (an object) that has been inserted within some other data (other object). An inset behaves exactly as if it were a separate document. The only difference is that it may not have scrollbars.
ez can be configured so that when a file is to be created, a certain inset will be the default. For instance, if you invoke ez on a file called test.d or test.doc, the menus will contain the text inset with menu items you need for writing a paper like this one. Of course, once the file has been created, ez will automatically use the insets indicated by the data itself. Similarly, editing a file called test.ras results in the raster inset being created. Editing test.html results in an html inset being created.
To create a new inset in a text document, move the cursor to where you want the inset to exist and select an item from the “Media” menu (or press Esc-Tab). In Figure 1, I selected the “raster” inset. The causes a raster object to be created, initially appearing as an empty box. Many insets (but not all) allow other insets to be embedded in them. After adding a raster inset, you are editing two documents—each with different attributes. Which “editor” (object) has control is based on where the cursor is positioned. In this example if you click in the raster box, the menu cards will change to those of the raster program. Click in the text area outside the box and the text menus return.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- LiveCode Ltd.'s LiveCode
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide