On Sunday 13 June 2004 03:15, Anders Johansson wrote:

On Sunday 13 June 2004 03.02, Doug McGarrett wrote:

...

kate won't work in root

Yes it will

Indeed: <Alt>-<F2> kdesu kate

...

, and kword is not recognized

by what?

But it's a good idea to learn vi (or vim) anyway. Sooner or later you'll find yourself on a system that has crashed and you need to rescue it, and vi is the only editor available.

in text mode: vi <file-to-edit> - move cursor to position - press <Insert> - use <Delete> to delete letters - enter text - press <Esc> - press ':wq' to w)write file and q)uit (no quotes) or press ':q!' to abandon the file & q)uit (no quotes) Cheers, Leen

On Sunday 13 June 2004 11:20, Jake wrote:

On Sunday 13 June 2004 02:15, Anders Johansson wrote:

...

But it's a good idea to learn vi (or vim) anyway. Sooner or later you'll find yourself on a system that has crashed and you need to rescue it, and vi is the only editor available.

Will pico not work under these circumstances? I find vi(m) a bit intimidating to be honest.

pico resides in /usr/bin while vi is in /bin and (I'm guessing) only /bin is available when attempting to rescue a system. So it looks like I'd best get over my inimidation problems and grasp the nettle.

On Sunday 13 June 2004 06:18, Johan Sch wrote:

On Sun, 13 Jun 2004 11:53:42 +0100

Jake wrote:

...

On Sunday 13 June 2004 11:20, Jake wrote:

...

On Sunday 13 June 2004 02:15, Anders Johansson wrote:

...

But it's a good idea to learn vi (or vim) anyway. Sooner or later you'll find yourself on a system that has crashed and you need to rescue it, and vi is the only editor available.

Will pico not work under these circumstances? I find vi(m) a bit intimidating to be honest.

pico resides in /usr/bin while vi is in /bin and (I'm guessing) only /bin is available when attempting to rescue a system. So it looks like I'd best get over my inimidation problems and grasp the nettle.

If I am stating the obvious here .. that is for the benefit of our really new users. I use gedit .. this is a very good editor .. absolutely easy to use .. if you ever used notepad in win .. well this is just better .. it prints also very nice if you want a hardcopy. Kwrite is also fine. ...BUT..to use the above you need to go in to console mode and.. sux - . password..this will make you su (need to be to edit fstab)and able to use GUI applications Enjoy

If I'm not mistaken (waits for the 'you are's', heh), mc is a good thing to learn to, and it's a lot easier than vi(m).

On Sunday 13 June 2004 00:18, Johan Sch wrote:

If I am stating the obvious here .. that is for the benefit of our really new users. I use gedit .. this is a very good editor .. absolutely easy to use .. if you ever used notepad in win .. well this is just better .. it prints also very nice if you want a hardcopy. Kwrite is also fine. ...BUT..to use the above you need to go in to console mode and.. sux - . password..this will make you su (need to be to edit fstab)and able to use GUI applications Enjoy

Not really. Kwrite , as root, use Alt-F2 and run it as a different user. Very easy. -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."

Good evening, Jake and others: (Some extraneous material erased.)

...

Will pico not work under these circumstances? I find vi(m) a bit intimidating to be honest.

Incidentally I had a go on a friends OSX laptop the other day and was amazed to find pico there (my friend was as amazed). But I guess it's not *that* suprising.

Jake

Pico seems to work. The file is altered. It didn't help. Thanx to all who answered. I have not tried gedit, but Kwrite does _not_ work--it comes back with the word "unique" in its error message, and a batch of other dreck. OK, I added "users" to the list in fstab for the floppy drive. I still get "Writing to drives is not supported" when I try to copy a file to a floppy. What's going on here? Do I need to reboot? As in MSWindows? Or is it just not possible to write to a drive in SuSE 9.1? --doug

Do the directory permissions allow write access. If not then the file permissions are irrelavant. CWSIV On Sun, 2004-06-13 at 17:26, Doug McGarrett wrote:

On Sunday 13 June 2004 19:46, Doug McGarrett wrote:

...

Good evening, Jake and others:

(Some extraneous material erased.)

So I rebooted the machine, and writing to drives is still not supported.

...

OK, I added "users" to the list in fstab for the floppy drive. I still get "Writing to drives is not supported" when I try to copy a file to a floppy. What's going on here? Do I need to reboot? As in MSWindows? Or is it just not possible to write to a drive in SuSE 9.1?

--doug

* Doug McGarrett [06-15-04 09:35]:

I'm not sure I understand the question. I'm not trying to write to a directory, I'm trying to write a file to a floppy disk. There are no permissins involved. AAMOF, the floppy is formatted in DOS.

Better go back to the books, especially file systems and permissions. Directory information is included. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

On Monday 14 June 2004 01.46, Doug McGarrett wrote:

I still get "Writing to drives is not supported" when I try to copy a file to a floppy.

I've greped for this error message but I can't find it anywhere. What exactly do you do to get it, and which program is it that tells you this?

On Tuesday 15 June 2004 01.10, Doug McGarrett wrote:

On Sunday 13 June 2004 20:29, Anders Johansson wrote:

...

On Monday 14 June 2004 01.46, Doug McGarrett wrote:

...

I still get "Writing to drives is not supported" when I try to copy a file to a floppy.

I've greped for this error message but I can't find it anywhere. What exactly do you do to get it, and which program is it that tells you this?

I go to someplace where I can snap on a file and say "copy" then I go to the This Computer (was "My Computer" before I got rid of stupid Windows nomenclature) and snap on "Floppy Disk" and try "Paste." This is the way a windows system is supposed to work. Then I get the message you see above.

Yeah, I've heard this from others too. But I can't for the life of me find which program generates the message. I can't reproduce it on my system, and I've greped through every binary I have. I simply can't understand where it's coming from In any case, it's nothing to do with ACLs (which by the way isn't a new feature), it works well from the command line - or so I'm told by the people who see this error. My best guess is that it's some problem with either subfs or the way konqueror interacts with it. But since I can't find the error, I can't say for certain

On Monday 14 June 2004 01:46, Doug McGarrett wrote:

Pico seems to work. The file is altered. It didn't help. ... OK, I added "users" to the list in fstab for the floppy drive. I still get "Writing to drives is not supported" when I try to copy a file to a floppy. What's going on here? Do I need to reboot? As in MSWindows? Or is it just not possible to write to a drive in SuSE 9.1?

You're right, there have been some important changes in SUSE Linux 9.1. I cannot write to a floppy either, and so far I could not figure out how I can. I've looked in the User Guide and in the Admin Guide: nope. Perhaps it is related to ACL (access control lists), a new feature. Anybody who knows more: please help. Cheers, Leen

On Saturday 12 June 2004 19:23, John Andersen wrote:

On Saturday 12 June 2004 17:02, Doug McGarrett wrote:

...

How?

Is there a simple text editor in SuSE that will edit root files (like fstab) or will I have to learn VI, or VIM, or emacs? (kate won't work in root, and kword is not recognized.) I used to be able to do this, perhaps with a different distro, years ago. Here again is my complaint that nothing is permitted, and there's no obvious way of changing that. I am the owner of this system, and I have the root password, but I can't seem to modify anything anyway.

I use Kwrite ( as root) for doing that and it works perfect. -- Greetings from /bill at 169 west , 19 south. Disclaimer: Any errors in spelling, tact, or fact are transmission errors."

On Sunday 13 June 2004 12:03, Georgios Tsarmpopoulos wrote:

Doug McGarrett wrote:

...

How?

Is there a simple text editor in SuSE that will edit root files (like fstab) or will I have to learn VI, or VIM, or emacs? (kate won't work in root, and kword is not recognized.) I used to be able to do this, perhaps with a different distro, years ago. Here again is my complaint that nothing is permitted, and there's no obvious way of changing that. I am the owner of this system, and I have the root password, but I can't seem to modify anything anyway.

--doug

There is a service menu for kde that will allow you to edit root files with kwrite. It's called Edit As Root and you can find it here: http://www.kde-apps.org/content/show.php?content=11998

The Readme file is unreadable, and just keeps unrolling, but never comes to a stop. Anyway, I have edited the file and still can't write to a floppy . --doug

Doug, etc: I prefer "joe" which ships with SuSE. Pico, and its open-source clone, "nano", have an annoying tendency to insert linewraps where they're not wanted. -- -Josh Berkus Aglio Database Solutions San Francisco

On Monday 14 June 2004 23:18, Josh Berkus wrote:

Doug, etc:

I prefer "joe" which ships with SuSE

"Joe" uses the standard key combinations of an old classic . . . Star-Writer, maybe?? Joe is my preferred Console Editor, too ................... best wishes ____________ sent on Linux ____________

On Monday June 14 2004 9:41 pm, Patrick Shanahan wrote:

* pinto [06-14-04 19:05]:

...

"Joe" uses the standard key combinations of an old classic . . . Star-Writer, maybe??

That would be WordStar from cp/m originally.

...

Joe is my preferred Console Editor, too

I thought PerfectWriter was a great app., till I used WordStar. Those were the days. :) Fred -- Ronald Reagan 1911 - 2004 An American Patriot who hated Communism and Socialism, never brought shame upon himself, his family, his political offices or abused the trust of the American People. We love you and we wonder when another like you or Theodore Roosevelt will arise again.

On Tuesday 15 June 2004 10:43, James Knott wrote:

Many years ago, I used to use WordStar 2000 at work and PC-Write at home.  I still have my PC-Write manual and licence...somewhere...

PC-Write ~ great little editor . . . was it written by Jim Button? -- best wishes ____________ sent on Linux ____________

On Tue, 2004-06-15 at 06:43, James Knott wrote:

Fred Miller wrote:

...

On Monday June 14 2004 9:41 pm, Patrick Shanahan wrote:

...

* pinto [06-14-04 19:05]:

...

"Joe" uses the standard key combinations of an old classic . . . Star-Writer, maybe??

That would be WordStar from cp/m originally.

...

Joe is my preferred Console Editor, too

I thought PerfectWriter was a great app., till I used WordStar. Those were the days. :)

Many years ago, I used to use WordStar 2000 at work and PC-Write at home. I still have my PC-Write manual and licence...somewhere... ;-)

And this has what to do with the original subject? I thought this was a list to help others with problems not who uses which editor. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)

The Tuesday 2004-06-15 at 06:46 -0000, pinto wrote:

"WordStar" . . . yes, < joe > uses WordStar key-combinations . . . I prefer < joe > , instead of < vi > for root admin jobs from Console

Me too. But for scripts I prefer "mcedit", because it has syntax highlighting - although I'm more confortable with jstar. Any way, knowing the basics of "vi" is a necesity. -- Cheers, Carlos Robinson

The Tuesday 2004-06-15 at 20:17 -0500, Patrick Shanahan wrote:

Have a look at jed, currently 0.99.16/Unix. Does macros, syntax highlighting, multiple buffers, screen splitting, ....

Has a mail mode with header and quote level highlighting, automatic deletion of existing sig's when replying, etc ....

Sounds very interesting - in fact, I tried it a while ago this morning -, but mine defaults to "emacs" mode, and that's an interface I'm not confortable with. Supposedly that behaviour can be modified: Wordstar Emulation ------------------ `wordstar.sl' contains the S-Lang code for JED's Wordstar emulation. Adding the line "wordstar.sl" evalfile pop to your `jed.rc' (`.jedrc') startup file will enable JED's Wordstar emulation. I did add that exact line (the .jedrc was empy), but I get an error: S-Lang Error: Syntax Error: Expecting ;: found 'evalfile', line 1, file: /home/cer/.jedrc I guess that line is not the line I have to paste :-/ -- Cheers, Carlos Robinson

The Wednesday 2004-06-16 at 10:36 -0500, Patrick Shanahan wrote:

locate jed.rc copy to ~/ modify section to read (Borland IDE, same as Wordstar):

...

note: only one line above does *not* begin with '%'.

syntax highlighting for mail entails activating email.sl

It works, thanks. :-) But I find the interface a bit awkward (down cursor in the menu does not open the dropdown, for example; ^KQ does not exit, etc. But worse, it does not have pascal syntax higlight, or it is not automatic :-/ I still use pascal O:-) - mcedit does have it, for example, or jedit (an editor in java!). I'll keep trying. -- Cheers, Carlos Robinson

The Wednesday 2004-06-16 at 19:35 -0500, Patrick Shanahan wrote:

...

But I find the interface a bit awkward (down cursor in the menu does not open the dropdown, for example; ^KQ does not exit, etc.

^KX

Yes; but ^KQ was "exit without saving", whereas ^KX was "exit and save" - no questions asked, or almost none. Well... it's just a question of getting used to it.

...

But worse, it does not have pascal syntax higlight, or it is not automatic :-/

I still use pascal O:-) - mcedit does have it, for example, or jedit (an editor in java!).

tpascal.sl %8^]

:-) Ah! Good. And I do have that file on my system. Now, how do I activate it? The configuration file says: WANT_SYNTAX_HIGHLIGHT = 1; % Highlight syntax in C, Fortran, and TeX modes. It doesn't mention anything else. Looking at "pinfo jed" I see: * Modes:: But it only talks about "wrap mode". It's not too helpfull... Ah, "info jed" shows more, I guess "pinfo" is broken. Let's see... * Wrap Mode:: * Smart Quotes:: * C Mode:: * Fortran Mode:: But it doen't say how to activate them. Lets try again, anyway. F10/Select mode: C mode S-Lang Text LaTeX TeX No Mode Fortran F90 Python sh No mention of pascal there. "F1" shows no help, it beeps. Not a simple case of RTFM :-) -- Cheers, Carlos Robinson

The Thursday 2004-06-17 at 06:56 -0500, Patrick Shanahan wrote:

Open ~/.jedrc at the bottom, add:

() = evalfile("tpascal.sl");

I understand the confusion. IANAP and I do not understand slang, but looked over the sample .jedrc and a few of the *.sl files provided and made a few trial runs. It worked 8-).

It doesn't work here, no colours :-( -- Cheers, Carlos Robinson

The Monday 2004-06-21 at 08:44 -0500, Patrick Shanahan wrote:

...

...

() = evalfile("tpascal.sl");

I understand the confusion. IANAP and I do not understand slang, but looked over the sample .jedrc and a few of the *.sl files provided and made a few trial runs. It worked 8-).

It doesn't work here, no colours :-(

Do /usr/local/jed/lib/tpascal.[dfa|sl|slc] exist?

Yep, but on a different place: cer@nimrodel:~> l /usr/share/jed/lib/tpascal.* -rw-r--r-- 1 root root 7810 2003-03-17 15:01 /usr/share/jed/lib/tpascal.dfa -rw-r--r-- 1 root root 5901 2003-03-17 15:01 /usr/share/jed/lib/tpascal.sl -rw-r--r-- 1 root root 4858 2003-03-17 15:01 /usr/share/jed/lib/tpascal.slc But I'm using the default version that came with suse 8.2, not one compiled locally, as yours seems to be (/usr/local): cer@nimrodel:~> jed --version jed version: 0.99.16/Unix Compiled with GNU C 3.3 S-Lang version: 1.4.8 jed compile-time options: +LINE_ATTRIBUTES +BUFFER_LOCAL_VARS +SAVE_NARROW +TTY_MENUS +EMACS_LOCKING +MULTICLICK +SUBPROCESSES +DFA_SYNTAX +ABBREVS +COLOR_COLUMNS +LINE_MARKS -GPM_MOUSE Using JED_ROOT=/usr/share/jed Oh, well, I'll be updating to suse 9.1 this week - hopefully - perhaps the version there has it (after I solve the heaps of new problems that updating will bring). -- Cheers, Carlos Robinson

The Monday 2004-06-21 at 19:46 -0500, Patrick Shanahan wrote:

I do not believe that SuSE includes it any more. You will have to build your own version. It was not included with 9.0 :^(.

Huh? That's surprising, it seems quite a good program.

pat@wahoo:~> jed --version jed version: 0.99.16/Unix Compiled with GNU C 3.3 S-Lang version: 1.4.9

jed compile-time options: +LINE_ATTRIBUTES +BUFFER_LOCAL_VARS +SAVE_NARROW +TTY_MENUS +EMACS_LOCKING +MULTICLICK +SUBPROCESSES +DFA_SYNTAX +ABBREVS +COLOR_COLUMNS +LINE_MARKS -GPM_MOUSE

They are the same options as I have. Ok, I'll wait till I upgrade. Mmm, and the same version - perhaps that's why SuSE dropped it, because developping has stopped? -- Cheers, Carlos Robinson

On Thursday 17 Jun 2004 00:57, Carlos E. R. wrote:

The Wednesday 2004-06-16 at 10:36 -0500, Patrick Shanahan wrote:

...

locate jed.rc copy to ~/ modify section to read (Borland IDE, same as Wordstar):

....

...

note: only one line above does *not* begin with '%'.

syntax highlighting for mail entails activating email.sl

It works, thanks. :-)

But I find the interface a bit awkward (down cursor in the menu does not open the dropdown, for example; ^KQ does not exit, etc. But worse, it does not have pascal syntax higlight, or it is not automatic :-/

I still use pascal O:-) - mcedit does have it, for example, or jedit (an editor in java!).

I'll keep trying.

-- Cheers, Carlos Robinson

from what i see the latest version of joe supports pascal as well as the normal suspects.. -- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan PGN

"Carlos E. R." [15 Jun 2004 17:24]:

Me too. But for scripts I prefer "mcedit", because it has syntax highlighting -

I'm not quite sure if the version of joe in 9.1 already has syntax hilighting, but the current CVS version of joe does have it :) Philipp

The Monday 2004-06-14 at 20:41 -0500, Patrick Shanahan wrote:

* pinto [06-14-04 19:05]:

...

"Joe" uses the standard key combinations of an old classic . . . Star-Writer, maybe??

That would be WordStar from cp/m originally.

Correct, and later for dos. The same set of key combinations was used by Borland's Turbo Pascal, and from then on, by all their IDEs to this day. And not only by them, I have seen quite a few editors using that set of keystrokes that I have so ingrained into my brain ;-)

...

Joe is my preferred Console Editor, too

Meetoo^n And it comes on five flavours: joe, jstar, jmacs, rjoe, jpico (pine's editor)... -- Cheers, Carlos Robinson

On Sunday 13 Jun 2004 02:02, Doug McGarrett wrote:

...

How?

Is there a simple text editor in SuSE that will edit root files (like fstab) or will I have to learn VI, or VIM, or emacs? (kate won't work in root, and kword is not recognized.)

Doug

? When you open konqueror in Super User Mode you can very happily use kwrite and kate. I had some problems with this in 8.2. Sometimes it was not allowed. Deleting .Xauthority in the /root directory did the trick as far as i can remember. Peter Vollebregt

On Sunday 13 June 2004 02:02, Doug McGarrett wrote:

...

How?

Is there a simple text editor in SuSE that will edit root files (like fstab) or will I have to learn VI, or VIM, or emacs? (kate won't work in root, and kword is not recognized.) I used to be able to do this, perhaps with a different distro, years ago. Here again is my complaint that nothing is permitted, and there's no obvious way of changing that. I am the owner of this system, and I have the root password, but I can't seem to modify anything anyway.

Apologies if this has already been posted, but SUSE wrote a great little script called "sux", which basically lets you run apps as root but it handles all the messy stuff with xauth and running as root in another account. Once again SUSE delivers nice little touches like this! It runs similarly to "su"... essentially you could enter: % sux -c /opt/kde3/bin/kate which says "run the command kate as root" - and it will ask you for the root password and away you go. Note you must pass the full path to the app you want since root doesn't have the kde binaries in it's path by default(for security reasons only - you could - unadvisedly - change this). You can always find out where apps are by typing, for example, % which kate which returns the location of kate. "sux" can also be used just like "su" - just type it in, give the password, and any X or otherwise commands you run will be run as root(or whoever you want). Also note that you are getting this behaviour for security reasons - just like windows you could set things up so a given account has admin abilities, but this isn't recommended. sux works very well in it's place. Cheers, J.C. -- John Coldrick www.axyzfx.com Axyz Animation Houdini/Renderman/Discreet 425 Adelaide St W 416-504-0425 Toronto, ON Canada jc@axyzfx.com M5V 1S4 ----------------------------------------------------------------------- Entropy isn't what it used to be.