From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Robert Thorpe Newsgroups: gmane.emacs.help Subject: Re: Help setting up POP3 email (rmail) Date: Wed, 24 Feb 2016 20:16:42 +0000 Message-ID: <87vb5d9845.fsf@robertthorpeconsulting.com> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1456345033 26639 80.91.229.3 (24 Feb 2016 20:17:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 24 Feb 2016 20:17:13 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Feb 24 21:17:02 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aYfro-0002Me-PO for geh-help-gnu-emacs@m.gmane.org; Wed, 24 Feb 2016 21:17:00 +0100 Original-Received: from localhost ([::1]:38129 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYfro-0002gu-4U for geh-help-gnu-emacs@m.gmane.org; Wed, 24 Feb 2016 15:17:00 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35356) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYfrc-0002gb-NZ for help-gnu-emacs@gnu.org; Wed, 24 Feb 2016 15:16:49 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aYfrZ-0000Mk-AY for help-gnu-emacs@gnu.org; Wed, 24 Feb 2016 15:16:48 -0500 Original-Received: from outbound-smtp12.blacknight.com ([46.22.139.17]:45658) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYfrZ-0000MW-4J for help-gnu-emacs@gnu.org; Wed, 24 Feb 2016 15:16:45 -0500 Original-Received: from mail.blacknight.com (pemlinmail03.blacknight.ie [81.17.254.16]) by outbound-smtp12.blacknight.com (Postfix) with ESMTPS id BAEA11C1EAF for ; Wed, 24 Feb 2016 20:16:43 +0000 (GMT) Original-Received: (qmail 19485 invoked from network); 24 Feb 2016 20:16:43 -0000 Original-Received: from unknown (HELO RTLaptop) (rt@robertthorpeconsulting.com@[93.107.66.221]) by 81.17.254.9 with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 24 Feb 2016 20:16:43 -0000 In-Reply-To: (cptvlaze@tutamail.com) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 46.22.139.17 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:109295 Archived-At: writes: > I have no idea, but emacs made it like this. ~/.emacs.d is owned by > root, which can do whatever he pleases with it. When you first started Emacs did you do it using sudo from your own home directory? I maybe that could cause .emacs.d to be owned by root. Anyway, I suggest the following, which is probably simpler than mucking about with chown: * In your normal user account copy the stuff you want out of .emacs.d. You probably only want init.el if you've just started. * Sudo and delete .emacs.d. * Recreate .emacs.d and copy init.el into it. * Run Emacs and it should work from your normal account. BR, Robert Thorpe > No one out of him can > do anything with the folder. I thought it was a normal configuration > made by the editor itself. I can chown it, though. Could you give me > the proper permissions that > I have to give it? (Intended for my personal laptop, which could be=20 > eventually used by other people, etc.) > > 24. Feb 2016 15:46 por tomas@tuxteam.de: > > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Wed, Feb 24, 2016 at 02:38:41PM +0000, > cptvlaze@tutamail.com> wrot= e: >> >> [...] >> >>> I also have a problem with my init file, as emacs can't detect it. I ha= ve >>> created one at ~/.emacs.d/init.el, but this folder is protected (only >>> accessible via su) >> >> This is a very strange thing to do. Why should something in your home >> be ony accessible by root? (why should it belong to root in the first >> place?). >> >> I mean: readable only by owner makes sense, but the owner should be >> *you*, I think. >> >> Regards >> - -- tom=C3=A1s >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.12 (GNU/Linux) >> >> iEYEARECAAYFAlbNwl8ACgkQBcgs9XrR2kYb+QCfZPoGx+S1cIGBwF4HxjMd1sIy >> aX4An1ZRgpbwg10FfNxMlqtYImAyPpzL >> =3D9ox7 >> -----END PGP SIGNATURE-----