[vox-tech] bash question - how to read specifed amnt of data from a file

[Jonathan Stickel]

Richard Burkhart wrote:
> It's "easier" for the same reason as it's easier in other clients -- you
> hit r)eply and you've got a message with the vox-tech address all nice
> and ready--just need to clear out the previous contents.  Quicker,
> easier, lazier.  And I don't remember if Outlook has a setting to thread
> replies on the email side. (Express probably threads in the
> newsreader--but who uses Usenet?  That's where all of them scary linux
> freaks hide out!) 
> 
> Unlike some other email clients (I'm assuming mutt and pine--haven't
> worked with those) - by my experience, the In-Reply-To field is almost
> impossible to get to.  You might be able to get to it using the OPTIONS
> menu, then "view message headers" ... but I don't know if you'd be able
> to edit that field.  (this opinion might be changed with infusion of
> coffee, so I can get my brain online and remember the actual path to
> it.)
> 
> On Thu, 2003-10-09 at 05:51, p@dirac.org wrote:
> 
>>hi dylan,
>>
>>please don't start a new thread by replying to a message.  always
>>compose a new message.  you broke the keymapping thread for me.
>>
>>i've noticed that outlook users are particular prone to starting threads
>>by replying ot old messages.  i'm curious -- in outlook, is it easier to
>>reply than to start a new message?

This is too tempting an opportunity to bash outlook users...

As Rich points out, it is always easier to hit "reply" than "compose", 
where you have to _manually_ type in a "to" address and a subject line. 
  This is true of most email clients.

But there _is_ a social correlation to outlook:  those who are too lazy 
to click compose are also the ones who are too lazy to explore 
alternative email clients to the default, but extremely faulty, email 
client bundled on their M$ system... ;)

Jonathan


>>
>>pete
>>
>>ps- there's a header "In-Reply-To:".  if you delete that header, you'll
>>be fine.
>>
>>
>>
>>On Wed 08 Oct 03, 10:49 PM, dylan <dylan@iici.no-ip.org> said:
>>
>>>hi-
>>>
>>>been playing around with using a basic stamp II to collect environmental
>>>data with very minimal setup (CdS cell and capacitor form an RC network, RC
>>>constant is measured by BS II)
>>>[http://surfdavis.no-ip.com/~dylan/light_level.p2.png]
>>>
>>>the BSII sends its data to /dev/ttyS0, and it is read in with the
>>>command'cat /dev/ttyS0 > tmp.light &' . data is parsed by a simple awk
>>>script and then sent to ploticus for a nice plot. the plot is updated by
>>>running a shell script that runs the awk sript and then ploticus.
>>>
>>>this works, but there is no way to associate a time with the data values. i
>>>was thinking that if there was some way to have a bash script read from
>>>/dev/ttyS0 every 10 seconds or so, save the value to a text file along with
>>>a date stamp it would be pretty neat.
>>>
>>>the output from the BSII looks something like this:
>>>light_level|light_level|light_level   and so on (the delimiter is a pipe)
>>>
>>>now to the question: does anyone know how to make bash read from a file
>>>(i.e. the serial port) from one pipe until another pipe, and then save the
>>>value in between to a text file?
>>>
>>>i know this is asking a lot, but any pointers would be great!
>>>
>>>thanks a lot!
>>>
>>>dylan
>>>
>>>_______________________________________________
>>>vox-tech mailing list
>>>vox-tech@lists.lugod.org
>>>http://lists.lugod.org/mailman/listinfo/vox-tech
>>
>>-- 
>>GPG Instructions: http://www.dirac.org/linux/gpg
>>GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D
>>_______________________________________________
>>vox-tech mailing list
>>vox-tech@lists.lugod.org
>>http://lists.lugod.org/mailman/listinfo/vox-tech
>>
> 
> 
> 
> _______________________________________________
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech
> 
>