--------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: CER00002 Date: 10/20/95 From: JAN VERMEULEN Time: 09:40pm \/To: RICHARD BLACKBURN (Read 5 times) Subj: Goodbye Quoting Richard Blackburn of 1:133/314 on 16 Oct 95 12:15:11 to All: > Dear SemWare Customer, etc. Thank you for all the good work, Richard, and good luck! -=<[ JV ]>=- --- * Origin: The Poor Man's Workstation -- Wormerveer NL (2:280/100) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: CER00003 Date: 10/19/95 From: BEN CARPENTER Time: 10:57pm \/To: CLAUS BRINCH JENSEN (Read 5 times) Subj: Re: Quote macro 1/2 (1) -=> Quoting Claus Brinch Jensen to Ben Carpenter <=- CBJ> I have also tried out the macro you posted and I am also having CBJ> trouble getting it to work. Claus I went back in my old files and found the message that Don Alt sent the macro in and am posting it. I am splitting it up in to two messages so that you do not miss some of it. The second one is still long so my BBS door may split that one also. QEDIT MACRO TO REFORMAT QUOTED PARAGRAPHS ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (or The macro Frank Sexton can't live without). For QEdit v3.0c or TSE Jr v4.0. This macro will NOT work in v2.xx of Qedit. How to use this Macro ~~~~~~~~~~~~~~~~~~~~~ 1. The macro works on one paragraph at a time. 2. There must be 1 blank line above, and 1 blank line below each paragraph, because it is these blanks lines that determine what a paragraph is. 3. The macro will not start: in the first line of a message; in the last line of a message; or in a blank line. 4. The marco can be started in any line of the paragraph... but ONLY in a line that contains the Fidonet defacto quote character, which is the greater-than ">" symbol. If you start the macro in a line which does not have the > symbol it give you a message, and abort. 5. If you are replying to a message where the person used a high ASCII character or some other fancy quote symbol other than the > symbol you will have to manually change the character or characters used to a > symbol in one line, and then delete all the rest of them in the other lines of the paragraph. Usually this is fastest to do by using Qedit's "find & replace" option, depending upon the size of the paragraph. 6. Long paragraphs can be *manually* split by people, like normal, into smaller sections. Each section can then be replied to individually or if unwanted, deleted out of the message. The purpose of quoting is to remind the person what the conversation is about, so there isn't a need to "over-quote" long, whole paragraphs if you will only reply to one small section of it. Most echo moderators frown on people who "over quote." 7. In long, multiple initial strings, such as: GH> MP>FS>LR> MM>EF> the macro captures and uses only the first initial string EF> and deletes the rest of the initials. The person who originally wrote what is quoted is identified by the EF> initial string, so all the other initials are unnecessary and only waste space and add costs for the SysOps carrying the echo. Having only the initials of the original writer saves space and money. 8. The macro will handle paragraphs with up to 12 lines in them... and I wouldn't try to use it on longer paragraphs, unless I split it into two smaller sections first. 9. This is NOT a "magic quote" or a "smart macro" or anything else. It's simply a Qedit macro. Some user brains are required to use it and at times, as noted above, manual editing of paragraphs might be required before using it. Example #1. From this: 1.Now is the time for all good men to party!2.Now is the time for all XX>good men to party. To this: XX> 1. Now is the time for all good men to party! 2. Now is the time for XX> all good men to party. NOTE: I *had* to start the macro in line 6 of that scrambled paragraph because that is where the initial string is located. Notice that the macro unscrambles the paragragh and removed the extra spaces in line #1; it added a space after the 1., the word party! and the 2. The macro also used column 76 as the right margin to wrap (reformat) the paragraph. Quotes should be a little longer than your normal right margin to save space, but you can change the margin to suit your tastes. --==<<< Continued next message >>>==-- --- MsgToss 2.0b * Origin: Lenawee PC Users Group RBBS Adrian, MI. 517-263-2061 (1:2470/19) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: CER00004 Date: 10/19/95 From: BEN CARPENTER Time: 10:58pm \/To: CLAUS BRINCH JENSEN (Read 5 times) Subj: Re: Quote macro 2/2 (1) Second part of message from Don Alt about Qedit macro to reformat quoted messages. <---- cut here ----> ***> Qedit macro to reformat QUOTED paragraphs. ***> For Qedit v3.0c and above. ***> Written by Don Alt on July 2, 1995. ^r IsEmptyLine MacroQuitTrue IsFirstLine MacroQuitTrue IsLastLine MacroQuitTrue BegLine TabRt BegLine " > " Loop01: CursorRight IsEndLine JTrue Loop02 IsCurrChar ">" JTrue Loop03 Jump Loop01 Loop02: BegLine DelCh DelCh " NEED INITIAL STRING> " DelRtWord BegLine UnMarkBlock MacroQuit Loop03: EndLine MarkLine Loop04: Find ">" Return "lb" Return Loop05: CursorLeft IsCurrChar " " JTrue Loop02 IsCurrChar "<" JTrue Loop04 IsCurrChar ">" JTrue Loop06 IsCurrChar #32 JTrue Loop07 Jump Loop05 Loop06: CursorRight " " CursorLeft Loop07: SaveSettings SetScreenOff SetInsMode SetAutoIndentMode SetRmargin "991" Return MarkBlockBegin Find ">" Return "i" Return CursorRight " " MarkBlockEnd Copy BegLine DelCh DelCh EndPara " " AddLine GotoColumn "996" Return MarkBlockEnd IsLastLine JFalse Loop08 AddLine BegLine " This _LAST_LINE_ needed by macro. Don Alt" Loop08: PrevPara TabRt BegLine MarkBlockBegin WrapPara PrevPara BegLine Loop09: WordRight Loop10: IsCurrChar " " JTrue Loop17 IsCurrChar ">" JTrue Loop11 CursorRight Jump Loop10 Loop11: CursorRight IsCurrChar #32 JTrue Loop12 " " Loop12: WordLeft Loop13: CursorLeft IsCurrChar "<" JTrue Loop14 IsCurrChar ">" JTrue Loop16 IsCurrChar #32 JTrue Loop16 Jump Loop13 Loop14: CursorLeft IsCurrChar #32 JTrue Loop15 CursorRight " " Loop15: WordRight WordRight CursorLeft Jump Loop09 Loop16: CursorRight DelRtWord DelCh Jump Loop10 --==<<< Continued next message >>>==-- --- MsgToss 2.0b * Origin: Lenawee PC Users Group RBBS Adrian, MI. 517-263-2061 (1:2470/19) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: CES00000 Date: 10/21/95 From: JORJ STRUMOLO Time: 02:31pm \/To: MIKE CHAMBERS (Read 4 times) Subj: TSE: bits and borders MC> There are dozens of features in TSE today > because one or two people asked for them. Features in TSE and marketing decisions by SemWare are different issues. Since we will not agree on the latter, it's dropped, and we'll stick to the former. I managed to internalize an activity I do whenever a file is unloaded, archive-bit wiping (previously I'd done a Dos() to wipe a file's archive-bit): proc ClearCFN() integer A A=FileExists(CurrFileName()) SetFileAttr(CurrFileName(),A & ~ _archive_) end This works, but I wonder why I can't simply do SetFileAttr(CurrFileName(),~ _archive_) -- possibly with a slightly different syntax if this isn't quite right, but this doesn't produce an error message, tho it also doesn't do anything. After all, I know the file exists already, and I don't care what the attributes are, I just want to assure the archive bit is wiped. Speaking of FileExists(), or any other command that would manage it, is there a way to test if a file, any file, exists in a directory (which will exist). Previously, FileExists() couldn't do that, since it reports the directory itself as a file, and no one could come up with a satisfactory way around that. It seems a simple question. Given C:\Tek\Tse\As\, do any files exist there, besides '.' and '..'? Another thing I've semi-internalized is video border setting. DESQview will retain frame colors, but won't start a new window with one unless it's explicitly told to, which used to require a batch file or alias. I've got TSE to now do a Dos() in Main() to do it, which saves a bit of time and memory. (I tried putting it in WhenLoaded(), but got various conflicts there.) How does DOS handle screen border colors, I wonder? Is there any way to do this with low-level stuff, instead of popping quickly out of the editor and then back in on a start under DV? -- SPEED 2.00 #1019: Anonymous was a woman. --- QScan/PCB v1.17b / 01-0175 * Origin: Eagle's Nest Comm., Inc Prov, RI 401-621-4600 (1:323/150) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: CET00000 Date: 10/21/95 From: JOAQUIM HOMRIGHAUSEN Time: 02:40am \/To: SEMWARE (Read 4 times) Subj: TSE 2.5, TSEjr/2 4.0 Awesome!!! :-) Got it in the mail today and have spent some time with both now. A couple of things: 1. I run with BRIEF.UI as my burnt-in UI. 2. The LISTOPEN macro should have "D-Delete" and "W-Write" (and technically, "E-Edit") for "Brief emulation". I'd also like the LISTOPEN macro to center its window on the screen. 3. I did this for TSE 2 and I'm doing it for TSE 2.5 :-) : proc SmartDosShell() string OurCurrentDrive[1] string OurCurrentDir[80] OurCurrentDir=CurrDir() OurCurrentDrive=GetDrive() Shell() LogDrive(OurCurrentDrive) ChDir(OurCurrentDir) end it's not really "smart" :-), but it does what I'd like it to do. Perhaps this can be included as an alternate shell.. 4. I can't get anything in regards to recent files, state, etc. to work. I've enabled all the options, but if I just enter E on the command-line, I get the "files to edit" input box, there is a TSEFILES.DAT in the TSE directory (where E.EXE is located), but that's about it [and yes, the .DAT file seems to be properly updated]. 5. The installation program uses double/single corner combo-characters, this doesn't look too cool under OS/2 with a non-437 code page selected. Either all double or all single works though - no big deal, but.. 6. I won't nag about the lack of real undo() since I'm sure you're getting tired of hearing it - but I will tell you that I still can't throw out Brief -- and apart from the above state stuff, this is now the only single reason I still have Brief on my disk. 7. I'd like TSE (and TSEjr/2) to support something like $[envvar] in any input field, any string, any .CFG setting, etc. to mean "replace with value of environment variable [envvar]". I often disconnect my machine from the LAN here, in which case I want my swap disk to be C:\TMP, when OS/2 is loaded, I want it to be H:\TMP, and when Novell is loaded, I want it to be X:\TMP. Now, I set TMP to this externally, so if I could tell TSE that my swap path is $[TMP], it'd "auto configure" itself depending on where I am. This obviously has other uses too. 8. I won't nag about the lack of TSE Pro/2 :-)) 9. How about a "state" option that does something like "Activate local state saving if state file exist in current directory, otherwise [disable | enable global]"? That way, I can force it to write a state file when I know I want one for a specific directory, but don't need it all the time. 10. BRIEF.UI again - Brief automatically unmarks the current block after it has been written to disk - TSE's BRIEF.UI doesn't. 11. I'm still a bit irritated about the fact that TSE cannot successfully process an "Access denied" error when attempting to open a file. If it gets Access Denied, I think it should try opening the file in READONLY/DENYNONE(/NOINHERIT). This has nothing to do with file locking, etc. it's simple common sense. I have applications running on other machines on the network and sometimes want to look at their logs, those files are opened in WRITEONLY/DENYWRITE/NOINHERIT, and TSE refuses to open them (TSEjr/2, however, does it). 12. If a file is opened in R/O mode (see [11, above]), TSE should display somewhere on the status line (and pref. set an internal variable) that the file or "buffer" has been opened in R/O mode and refuse to save it. That'll be it for now, I shall be back (famous last words :-)) And, keep up the excellent work - I'm only nagging about all this because I *WANT* to use TSE and TSEjr/2 (and TSE/2 :-), not because I think they're bad products. %JoHo% joho@abs.lu --- * Origin: Absolute Solutions (2:270/17.1) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: CET00001 Date: 10/21/95 From: JOAQUIM HOMRIGHAUSEN Time: 02:50am \/To: SEMWARE (Read 4 times) Subj: TSE 2.5, TSEjr/2 4.0 The CALENDAR macro should use single-only or double-only line characters (optionally I guess) for OS/2 VDMs, perhaps it could source the line drawing set from TSE's config somehow? %JoHo% joho@abs.lu --- * Origin: Absolute Solutions (2:270/17.1) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: CET00002 Date: 10/20/95 From: LEWIN EDWARDS Time: 07:29pm \/To: ALL (Read 4 times) Subj: QEdit (when it WAS QEdit) QEdit seems to be really good at breaking our software products. As part of our security package we are creating a write-only directory (yes, write-only). The problem is, that if someone creates a file (using anything), eg COPY FRED.TXT C:\DROPBOX [the name of the directory], if they try to load the filename with QEdit, they get an "editing new file" message and no file, *but* even if they exit straight out without saving, the original file is gone. What is our program doing ? Well, it fails the following DOS functions : * FCB & handle FindFirst * All FCB read functions * Handle opens in R/O or R/W mode are converted into W/O mode opens Of itself it's not such a major problem (though lots of places have QEdit lurking about). HOWEVER, if other things work the same way... What is QEdit doing ? (2.15 and 3.00) } Gates : 1 inadequate man. 1 inadequate vision. Many inadequate products. } Telstra (0419) 320415 * Optus (0412) 809805 * Vodafone (0414) 927056 --- GoldED 2.41+ * Origin: ZWSBBS +61-3-9827-6881 28800bps Multiline (3:634/396) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: CET00003 Date: 10/22/95 From: JACK DANIELS Time: 12:13pm \/To: MIKE CHAMBERS (Read 5 times) Subj: Re: ill winds Quoting Mike Chambers to Jorj Strumolo: Edited for brevity: MC> 3) If you want to print off the new features, that's easy: MC> 1. press MC> 2. select your topic MC> 3. press the grey+ key // copies the help text to your MC> clipboard 4. press esc // exit help MC> 5. press the grey* key // paste the block to your buffer MC> 6. print the block // prints it MC> 7. delete the block MC> In fact, you could accumulate the topics and print them in what ever MC> fashion you like. Hi Mike, Hmmm, think the above steps could be included in a macro that traverses the entire help system in TSE? For example, selects the first help topic in help, completes the steps outlined above, prints the topic to a file, and then selects the next help topic? This process would continue until all help topics had been written to disk, either under the help topic name, or in a single text file. **Hint Hint** to any and all TSE macro pros out there! Like most blind PC users, I prefer ASCII documentation-- there are just too many utils already out there for searching/retrieving information from text files. I know someone will say that V2.5 already has a searchable help system, but I'm currently using V2.0. In order to gain the equivalent access to the contents of the printed manuals, I currently must scan and process the manuals through my OCR software package. This requires that I chop apart the manuals so I can send them through the doc feeder on my HP scanner. The final output even with some cleanup is only about 95% accurate. Not bad, but it sucks when it comes to studying the macro language in any great detail! Anyway, anybody up to attempting the above mention macro? Let's hear from ya'll! Regards, Jack Internet: jterm9@infi.net ... A stitch in time saves embarassing exposure... --- Blue Wave/Max v2.20 * Origin: HandiNet B B S Virginia Beach, VA (804)496-3320 (1:275/429) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: CEU00000 Date: 10/22/95 From: ROELAND JANSEN Time: 10:23am \/To: MIKE CHAMBERS (Read 4 times) Subj: ill winds > JS> "Hope this Helps!" JS> popular of late, and one which I loathe> or "Thank you for your > JS> input." > This has not been my experience. SemWare has been > incredibly receptive to > user requests. There are dozens of features in TSE today > because one or two people asked for them. you bet. I have seen it happen with the development cycle of v1.00 -> v2.00 and v2.00 to v2.5. --- FastEcho v1.45a+ * Origin: [PC-MOS/386 operating system support] (2:2802/105.1) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: CEU00001 Date: 10/22/95 From: MARCUS LIMOSANI Time: 11:30am \/To: ROELAND JANSEN (Read 4 times) Subj: TSE 2.50 Gday Roeland 16 Oct 95 05:26, Roeland Jansen wrote to Marcus Limosani: >> to indicate to me that they are important and should not be >> deleted. This has caused some problems... >> One file I have is called -RAPATH.BAT, which is my path >> statement. RJ> ok, understandable that this will cause trouble with programs that use RJ> '-' as the separator for options. you could however change it by reating RJ> a few batchfiles that copy the file you wan to edit, edit it, and copy RJ> back. While annoying, i just renamed the batch file with a character that wasn't part of the command line. I know call it !RAPATH.BAT TTYL Marcus Limosani. marcusl@melbpc.org.au Fidonet : 3:633/262 --- FastEcho 1.45/RA 2.02+ * Origin: The Infinity Links BBS (3:633/262)