From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: <cptvlaze@tutamail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Help setting up POP3 email (rmail)
Date: Wed, 24 Feb 2016 20:16:42 +0000 [thread overview]
Message-ID: <87vb5d9845.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <KBIulvR--3-0@tutamail.com> (cptvlaze@tutamail.com)
<cptvlaze@tutamail.com> 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
> 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> wrote:
>>
>> [...]
>>
>>> I also have a problem with my init file, as emacs can't detect it. I have
>>> 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ás
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.12 (GNU/Linux)
>>
>> iEYEARECAAYFAlbNwl8ACgkQBcgs9XrR2kYb+QCfZPoGx+S1cIGBwF4HxjMd1sIy
>> aX4An1ZRgpbwg10FfNxMlqtYImAyPpzL
>> =9ox7
>> -----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-02-24 20:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 19:21 Help setting up POP3 email (rmail) cptvlaze
2016-02-23 22:41 ` Emanuel Berg
2016-02-24 0:41 ` Robert Thorpe
2016-02-24 2:50 ` Nick Dokos
2016-02-24 3:11 ` Emanuel Berg
2016-02-24 16:41 ` Nick Dokos
2016-02-24 14:38 ` cptvlaze
2016-02-24 14:46 ` tomas
2016-02-24 15:34 ` cptvlaze
2016-02-24 20:16 ` Robert Thorpe [this message]
2016-02-24 20:28 ` Robert Thorpe
2016-02-24 23:56 ` Emanuel Berg
2016-02-24 23:47 ` Emanuel Berg
2016-02-26 18:46 ` cptvlaze
2016-02-26 19:57 ` Emanuel Berg
2016-02-26 23:56 ` cptvlaze
2016-02-27 0:06 ` John Mastro
2016-02-27 4:05 ` Emanuel Berg
2016-02-27 8:28 ` tomas
2016-02-27 9:55 ` Eli Zaretskii
2016-02-28 2:11 ` Emanuel Berg
2016-02-28 17:52 ` Robert Thorpe
2016-02-29 0:20 ` Gnus (was: Re: Help setting up POP3 email (rmail)) Emanuel Berg
2016-02-29 2:31 ` Robert Thorpe
2016-03-02 2:28 ` Emanuel Berg
2016-02-29 0:55 ` Help setting up POP3 email (rmail) Emanuel Berg
2016-02-29 8:47 ` tomas
2016-02-27 0:44 ` Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
2016-02-27 10:24 Joe Westlaw
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb5d9845.fsf@robertthorpeconsulting.com \
--to=rt@robertthorpeconsulting.com \
--cc=cptvlaze@tutamail.com \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).