On Sun 2017-01-08 (20:26), Kevin O'Gorman wrote:
> If I knew what the "what" is, I might do it, but I'm clueless.
>
> On Sun, Jan 8, 2017 at 2:38 PM, Ulli Horlacher <
> frams...@rus.uni-stuttgart.de> wrote:
>
> > On Sun 2017-01-08 (12:57), Kevin O'Gorman wrote:
> >
> > > Fstools are interesting.
If I knew what the "what" is, I might do it, but I'm clueless.
On Sun, Jan 8, 2017 at 2:38 PM, Ulli Horlacher <
frams...@rus.uni-stuttgart.de> wrote:
> On Sun 2017-01-08 (12:57), Kevin O'Gorman wrote:
>
> > Fstools are interesting. I wonder why they are not in Ubuntu repos?
>
> Simply, because
an additional step is necessary
to get them to work without having to jump through hoops.
The only hoop is setting $PATH.
Everbody working with the shell should know what $PATH is.
If you do not know what a shell is, then fstools is nothing for you.
Actually, I did know just enough to get the
On Sun 2017-01-08 (14:12), pereira wrote:
> > You can download fstools or part of them manually from
> > http://fex.belwue.de/fstools/
>
> get -O- http://fex.belwue.de/sw/share/fstools-0.0.tar | tar xvf -
>
> This worked without problem, except that the executables ended up in a
> local
On Sun 2017-01-08 (12:57), Kevin O'Gorman wrote:
> Fstools are interesting. I wonder why they are not in Ubuntu repos?
Simply, because nobody has done it.
So, just do it!
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart
On Sun, Jan 8, 2017 at 4:42 AM, Ulli Horlacher <
frams...@rus.uni-stuttgart.de> wrote:
> On Thu 2017-01-05 (09:19), Kevin O'Gorman wrote:
>
> > I made what I thought was a minimal edit to
> > ~/.config/menus/xfce-applications.menu,
> > just moving one line down in a "layout" section. Immediately
Fstools are interesting. I wonder why they are not in Ubuntu repos? FSF
says their license is compatible with GPL.
On Sun, Jan 8, 2017 at 6:24 AM, Richard Owlett wrote:
> On 1/8/2017 6:42 AM, Ulli Horlacher wrote:
>
>> On Thu 2017-01-05 (09:19), Kevin O'Gorman wrote:
>>
On 01/08/2017 12:06 PM, Ulli Horlacher wrote:
On Sun 2017-01-08 (11:22), pereira wrote:
Trying to learn some more, I tried sudo apt get install sw,
and sudo apt-get install swtools, but nothing useful happend.
/sw is a UNIX software distribution system developed at the University of
On 1/8/2017 10:05 AM, Len Philpot wrote:
TECO ... fondly?:-) :-)
It did teach me to watch my punctuation. IIRC it was a misused
comma or semicolon in an edit macro that put me in an infinite loop.
Besides its what was available in the department at the time -
was an Engr Tech at DEC at
You're right - sloppy wording on my part. More accurate would be
"for-terminal-use". For example, $PS1 and other terminal related stuff.
That is,things I want set typically for all terminal instances.
That's based on the bash manpage I read somewhere back on Solaris years
ago. It said that
Hi Uri,
Real Unix Men were once little children too, and passed through various
stages as they
developed their magical powers in dealing with xubuntu or more in
general unix.
Others, though, became Real Expert Men in other areas, never having had
the time
or the motivation to learn other OSs
On Sun 2017-01-08 (10:02), Len Philpot wrote:
> For bash, I usually put per-terminal-instance values in ~/.bashrc
No good idea, because *every* bash subshell will execute ~/.bashrc, not
only when you start a new terminal program!
You can see it, when you add the line
echo executing ~/.bashrc
FWIW, I put Chrome in Areca's config file and it still didn't work. I
even repointed the /usr/bin/firefox symlink to Chrome and it worked
pretty much everywhere else, butnot in Areca: With /usr/bin/firefox
symlinked to Chrome, nothing happens from Areca. Oh well, good thing
I've read the help
TECO ... fondly?:-) :-)
I think I tried it once... kinda like EMACS. Just once. I do vi for
quick stuff all over the place, but even so I'll jump to (e.g.) Geanyfor
longer-term editing. However, use vi on Solaris for while and it'll make
you appreciate Vim greatly. :-)
*Len Philpot*
On 01/08/2017 09:24 AM, Ulli Horlacher wrote:
Environment variables like PATH must be placed in /etc/profile or
$HOME/.profile
$HOME/.bash_aliases is for - oh-wonder! - bash aliases!
Do not mix them!
You'll get a lot of varied opinions on this kind of topic, but
~/.profile is actually
On 1/8/2017 8:50 AM, Ulli Horlacher wrote:
On Sun 2017-01-08 (08:24), Richard Owlett wrote:
http://fex.belwue.de/fstools/del.html
I would suggest that any new to Linux browse
http://fex.belwue.de/fstools/index.html just to gain perspective
of what can be done at the command line.
Beware!
On Sun 2017-01-08 (10:00), pereira wrote:
> the web site downloads
> and installs all the 193 (IIRC) files in the fstool directory. That's easy.
>
> But, to make use of them you have to know some linux magic that is not
> described anywhere
Of course, one should know what $PATH is (for)!
This
FWIW, thh ones I tried (del and df3) work fine.
Pointing and clicking on an almost invisible command at the bottom of
the web site downloads
and installs all the 193 (IIRC) files in the fstool directory. That's easy.
But, to make use of them you have to know some linux magic that is not
On Sun 2017-01-08 (08:24), Richard Owlett wrote:
>> http://fex.belwue.de/fstools/del.html
> I would suggest that any new to Linux browse
> http://fex.belwue.de/fstools/index.html just to gain perspective
> of what can be done at the command line.
Beware!
This is only for Real Men [TM]
On 1/8/2017 6:42 AM, Ulli Horlacher wrote:
On Thu 2017-01-05 (09:19), Kevin O'Gorman wrote:
I made what I thought was a minimal edit to
~/.config/menus/xfce-applications.menu,
just moving one line down in a "layout" section. Immediately all my window
decorations went blank, and I could not so
On Thu 2017-01-05 (09:19), Kevin O'Gorman wrote:
> I made what I thought was a minimal edit to
> ~/.config/menus/xfce-applications.menu,
> just moving one line down in a "layout" section. Immediately all my window
> decorations went blank, and I could not so much as start a terminal
> emulator.
21 matches
Mail list logo