From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/31629 Path: main.gmane.org!not-for-mail From: Jorge Godoy Newsgroups: gmane.emacs.gnus.general Subject: Re: Suggestion for "file" mail-backend (was Re: nov and procmail compatability?) Date: 03 Jul 2000 15:13:49 -0300 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: main.gmane.org 1035168018 15205 80.91.224.250 (21 Oct 2002 02:40:18 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 02:40:18 +0000 (UTC) Cc: ding@gnus.org Return-Path: Original-Received: from fisher.math.uh.edu (fisher.math.uh.edu [129.7.128.35]) by mailhost.sclp.com (Postfix) with ESMTP id C1479D0520 for ; Mon, 3 Jul 2000 14:13:54 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by fisher.math.uh.edu (8.9.1/8.9.1) with ESMTP id NAC05486; Mon, 3 Jul 2000 13:10:10 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Mon, 03 Jul 2000 13:09:11 -0500 (CDT) Original-Received: from mailhost.sclp.com (postfix@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id NAA07342 for ; Mon, 3 Jul 2000 13:09:00 -0500 (CDT) Original-Received: from dagon.conectiva (brutus.conectiva.com.br [200.250.58.146]) by mailhost.sclp.com (Postfix) with ESMTP id 3685CD0520 for ; Mon, 3 Jul 2000 14:09:29 -0400 (EDT) Original-Received: by dagon.conectiva (Postfix, from userid 0) id 758A71F686; Mon, 3 Jul 2000 15:13:50 -0300 (BRST) Original-To: Harry Putnam X-URL: In-Reply-To: Harry Putnam's message of "03 Jul 2000 10:52:16 -0700" Original-Lines: 39 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:31629 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:31629 Harry Putnam writes: > I found this out (Per's observation) doing exactly what is suggested > above, but it can still work. Since I'm elisp impaired I set the var > `custom-file' for a session, to a separate file all-together > `~/tmp.el'.=20 >=20 > Do whatever customizing thing it is and write it to that file. As Per > says the whole mass of what emacs knows as done in customize is > written to the file too. But with some care you can pick out the new > stuff, and transfer it wherever. This is a good technique for elisp > impaired users, to see what the code is supposed to look like. Then, what's the difference of letting Customize write to you .emacs file and cutting of what isn't needed?=20 The problem is that you'll have to edit the output anyway...=20 I'll keep editing things by hand. And, for people who do that, the ":path" problem is still present. I don't know what is better: leaving everything in .emacs (newbie using Customize), making Customize a little smarter placing a "(load file.el)" in .emacs and adding everything to this file, making Customize a _smart_ tool and besides doing that creating a file for each main group, or, the last choice, editing things by hand. The best solution for newbies would be having Customize to put changes in one file per group. The best thing for experienced users would be grabbing his newbie configuration from these files, cutting off what's not needed and saving them. Elisp hackers would still be able to write things by hand ;-) See you, --=20 Godoy. =20 Departamento de Publica=E7=F5es Publishing Department Conectiva S.A.