On Wednesday 26 December 2001 23:39, [EMAIL PROTECTED] wrote: > debian-user-digest Digest Volume 101 : Issue 2478 > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > Today's Topics: > Re: Shell script for clients email b [ Alvin Oga > <[EMAIL PROTECTED] ] Re: man v. info [ > "Karsten M. Self" <[EMAIL PROTECTED] ] Re: Shell script for clients email b > [ "Karsten M. Self" <[EMAIL PROTECTED] ] Re: kernel compile problems > [ Sean Johnson <[EMAIL PROTECTED]> ] Re: Where do you RTFM ? > [ Brian Nelson <[EMAIL PROTECTED]> ] Re: User process killer > script.. [ k l u r t <[EMAIL PROTECTED]> ] RE: man v. info > [ Paul 'Baloo' Johnson <[EMAIL PROTECTED] ] Re: Where do you RTFM ? > > [ "Karsten M. Self" <[EMAIL PROTECTED] ] Re: Where do you RTFM ? > [ Erik Steffl <[EMAIL PROTECTED]> ] Re: kernel compile > problems [ Marc Wilson <[EMAIL PROTECTED] ] sound blaster > [ Mike Atamas <[EMAIL PROTECTED]> ] Re: sound > blaster [ Paul 'Baloo' Johnson <[EMAIL PROTECTED] ] Re: > ssh > and X [ "Jens =?iso-8859-1?q?M=FCller?=" <j ] Is > there mutt browseable Maildir sol [ Patrick Hsieh <[EMAIL PROTECTED]> ] > Don't replace manpages_1.46-1_all.de [ Yury Lyakh <[EMAIL PROTECTED]> ] Re: > Is there mutt browseable Maildir [ Rudy Gevaert <[EMAIL PROTECTED]> ] > Re: Where do you RTFM ? [ (Ted Harding) <[EMAIL PROTECTED] > ]
---------------------------------------- Content-Type: TEXT/PLAIN; charset="us-ascii"; name="Re: Shell script for clients email broadcast.." Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- > on Tue, Dec 25, 2001 at 06:32:31PM -0800, Craig Dickson ([EMAIL PROTECTED]) wrote: > > Carl Fink wrote: > > > BTW, for HTML docs, put them all in *one* file with hyperlinks. There > > > is no meaningful advantage to cutting it into twenty pieces, and it > > > makes searching significantly more difficult. > > > > For locally-stored docs that's arguable. The advantage of small files > > comes when you have to read it across a network, especially a WAN. > > I'd disagree. Info nodes can be _quit_ small -- a screen or less of > data. Load latency kills you more than the actual data transfer > interval. I'd rather have, say, 1/10 the interrupts, of roughly 2-4 > times the duration, than to be interrupted with great frequency. > > This can be further mitigated by browsers that render on partial load, > or which allow background loading of pages (Galeon rocks for this). > > > When I want to search a directory of HTML files, I tend to grep it > > first, then view the files that seem to be apropos. > > One better: > > $ less $( grep -l 'pattern' filelist ) > > Peace. ---------------------------------------- Content-Type: application/pgp-signature; charset="us-ascii"; name="Attachment: 3" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- > on Wed, Dec 26, 2001 at 03:55:41AM -0800, Petre Daniel ([EMAIL PROTECTED]) wrote: > > Ok,this may sound a bit twisted but i dont know very well shell scripting > > and i have the following problem: > > > > i have around 700 accounts on my school server and i want to send email > > to everyone of them from time to time with news related to the school and > > stuff.. I thought i can make an account and put in its homedir .forward > > file all the addresses > > > > I need a script that if run, checks all /home accounts and put them > > like [EMAIL PROTECTED] in the .forward of my > > email-broadcast-account. Or is there another simple way? > > Simpler? Dunno. Other? Sure. > > - Use a mailing list, e.g.: Mailman. > Pro: This is what it's designed for. Highly configurable. > Con: A modicum of setup is involved. > > - Use an MUA mail alias (within your mailer, e.g.: mutt) > Pro: Simple > Con: Alias is expanded in mailer, all addressees see all others, > unless Bcc'd or similar. > > - Use an MTA mail alias (within your mail daemon, e.g.: exim) > Pro: Reasonably simple. Conceals/supresses recipient addresses. > Con: Requires root access. May be accessible to outsiders if your > box can be used as a relay. > > > You could also use a shell script and a recipients list: > > $ vi body # message body > $ find /home -type d -maxdepth 1 | xargs -n 1 basename > whoto > $ for i in $( cat whoto ); do mail -s "Subject" $i < body; done > > > I'd probably opt for the Mailman option, particularly considering once > you've set up one list, you'll likely have requests for others. > > Peace. ---------------------------------------- Content-Type: application/pgp-signature; charset="us-ascii"; name="Attachment: 5" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- ---------------------------------------- Content-Type: text/plain; charset="us-ascii"; name="Attachment: 6" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- ---------------------------------------- Content-Type: application/pgp-signature; charset="us-ascii"; name="Attachment: 7" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- ---------------------------------------- Content-Type: text/plain; charset="us-ascii"; name="Re: Where do you RTFM ?" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- ---------------------------------------- Content-Type: text/plain; charset="iso-8859-1"; name="Re: User process killer script.." Content-Transfer-Encoding: 8bit Content-Description: ---------------------------------------- ---------------------------------------- Content-Type: TEXT/PLAIN; charset="us-ascii"; name="RE: man v. info" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- > on Tue, Dec 25, 2001 at 10:55:10PM -0500, Brian Nelson ([EMAIL PROTECTED]) wrote: > > "Karsten M. Self" <kmself@ix.netcom.com> writes: > > <...> > > > > I don't dislike emacs keybindings per se (I find most legacy MS > > > Windows- centric word processors unusable because I expect to find > > > C-a, C-e, C-k, C-p, C-n, C-s, C-r, etc., on them. Abiword's > > > supposed to have an emacs mode though I haven't got it to work). > > > That said, I find vi a more comfortable editor generally. > > > > The thing that really bothers me about vi is that it's very > > QWERTY-centric and feels very awkward with another layout, like > > Dvorak. The most often-used keys are chosen due to their position in > > the home row, and are completely meaningless in any other context (for > > example, j moves down, k moves up???). > > I have to agree. I taught myself Dvorak at one point (about ten days to > get over the hump), and found it worked relatively well for text > editing in, say, a standard word processor. But it absolutely blows > chunks with vi. > > The problem isn't just vi, though. _Most_ Unix commands are based on > mnemonic, consonant-heavy, abbreviations: ls, cd, rm, mv, ll, who, vi, > ps, mutt, df.... Most of these are balanced between left and right > hands, leading to good natural rhythems, many are based on home-row > keys, etc. Two of the most annoying Dvorak keytrokes are 'ls' (both > right pinky) and 'cd' (right middle top row, right index home left > reach). It sounds trivial, but you end up typing these repeatedly, and > the motor memory is hard to break. > > > Emacs' key bindings, however, are not aimed toward any particular layout > > but instead are often chosen as abbreviations of English words (C-n = > > next line, C-p = previous line, C-s = search, etc.). Since the Dvorak > > layout has the most commonly used letters in the home position, these > > key bindings tend to feel more natural on Dvorak (at least to me). > > Interesting, hadn't considered that. Then again, who wants to > remember that escape-x-alt-control-left shift-b puts you into > super-edit-debug-compile mode? ;-) > > I've always found the emacs keystrokes to be considerably > _anti_-ergonomic. Pessimal, really. > > Peace. ---------------------------------------- Content-Type: application/pgp-signature; charset="us-ascii"; name="Attachment: 12" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- ---------------------------------------- Content-Type: text/plain; charset="us-ascii"; name="Re: Where do you RTFM ?" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- > On Tue, Dec 25, 2001 at 10:53:06PM -0500, Sean Johnson wrote: > > The current binutils in sid is fine for compiling 2.4.17 (latest 2.4.x > > stable kernel). > > It's not binutils that have the problem... it's the kernel. Use a 2.4.17 > or later kernel if you want to avoid the error showing up most of the time. > The fixes contiue as well... I saw in the kernel mailing list that another > one of them was identified and fixed. It'll probably take a while. > > See lkml for the gory details. ---------------------------------------- Content-Type: application/pgp-signature; charset="us-ascii"; name="Attachment: 15" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- ---------------------------------------- Content-Type: text/plain; charset="iso-8859-1"; name="sound blaster" Content-Transfer-Encoding: 8bit Content-Description: ---------------------------------------- ---------------------------------------- Content-Type: TEXT/PLAIN; charset="us-ascii"; name="Re: sound blaster" Content-Transfer-Encoding: 7bit Content-Description: ---------------------------------------- ---------------------------------------- Content-Type: text/plain; charset="iso-8859-1"; name="Re: ssh and X" Content-Transfer-Encoding: quoted-printable Content-Description: ---------------------------------------- > Hello list, > > I am running Debian 3.0(woody) with mutt, courier-imap and postfix with > Maildir. Everything is working well, but I can't find the solution for > mutt to browse Maildir subfolders. Any solutions? ---------------------------------------- Content-Type: application/pgp-signature; charset="big5"; name="Attachment: 20" Content-Transfer-Encoding: 7bit Content-Description: ----------------------------------------
