> The Quick'n'dirty way to do this in vi is as follows:
>
> 1. Open the dos text file in vi.
> vi dosfile.txt
> 2. Type the following:
> :%s/^M//g
> ...where you "compose" the ^M character by pressing Ctrl+v then Ctrl+m
> 3. Save the file:
> :w New.Unix.File.txt
If you have
> Kill off those little gnome-* processes one at a time and see what goes
> away. This usually isn't fatal. You can restart them from an xterm and
> be back where you started. Killing off gnome-session will log you out,
> though :-)
> If you're not happy about killing things, stop them with '
Don't worry about it.
The free memory means that the kernel isn't using that RAM for anything
better; notice after you ran the program the buffers and caching went up.
So, if you try running that program again, you should notice (1) that it
starts up faster (since it's cached) and (2) if you ran
On Fri, 16 Jun 2000, Nancy Corbett wrote:
>
> When I want to repeat a search, I just hit the n key.
>
Yes, you can do this action in vim, and pressing 'N' to search backwards.
You can also prepend n / N with a count to search that many forwards /
backwards. However, I do not think vi suppo
> Is this correct?
>
> if ($string1 =~ /\*\s*\$string2|\$string2/)
^^^^
Looks like you're escaping the variable, you're searching for a literal
dollar sign rather than the value of $string2.
// jt
___
t
Hi, I've had this problem for a bit and it's driving me crazy.
I'm the webmaster and designer for my church's webpage, atlantanewhope.org.
Now, here's the deal - the page displays fine under Netscape and Explorer,
but looks all ugly under two browsers - Mozilla, and IE for Mac. Now, as I
underst
This is the situation between KDE and QT, as interpreted by Debian.
Troll Tech's QT library can be redistributed QT if it's unchanged and along with
the QT license.
However, KDE, is under GPL. It states that if you link GPLed KDE code against
the QT library and distribute it, you must distribut
> > Maybe so. But another issue is that KDE has incorporated a lot of
> > non-KDE-written GPL'd code, without asking the authors if it was ok to link
> > their code with Qt. In essence, forcing their controversial interpretation
> > of the GPL on other peoples' "products".
> And the GNOME proje
> > > And the GNOME project hast included some of the KDE code, thus, the
> > > relevant programs obviously are part of a chain reaction.
> >
> > No, you do not need permission to link GPLed (KDE) code against GPLed
> > (Gnome) code.
>
> Of course not -- but as soon as you take GPLed code from
tring? The BASH version is 2.04.
I'm willing to bet that BASH figures out your name once with the \u call,
while putting commands into your PS1 prompt will cause that command to be
executed with each prompt you ask for. Because the the "whoami" command
e
10 matches
Mail list logo
