From: Hans Hagen <pragma@wxs.nl>
Subject: Re: immediate write
Date: Mon, 01 Dec 2003 17:53:22 +0100 [thread overview]
Message-ID: <6.0.0.22.2.20031201175306.01e20e48@server-1> (raw)
In-Reply-To: <6.0.0.22.1.20031201165748.01b8b6b0@digitpaint.nl>
At 17:01 01/12/2003, you wrote:
>Hi,
>
>I ought to write information to a temporary file using immediate write ....
>
>The information concerned is placed on more than one line, but afterwards
>the info in the temp-file will have a single line only. So I loose all my
>new-line commands.
>
>Is there a way to keep those new-lione commands while using immediate write?
that's what buffers do ...
Hans
prev parent reply other threads:[~2003-12-01 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 16:01 Willi Egger
2003-12-01 16:53 ` Hans Hagen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6.0.0.22.2.20031201175306.01e20e48@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).