[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: my .muttrc is locked (i.e., read-only)



On Thu, Dec 19, 2002 at 05:47:17PM -0800, Osamu Aoki wrote:
> On Fri, Dec 20, 2002 at 01:18:39AM +0000, p wrote:
> > debs,
> > 
> > my .muttrc is "read-only."  i need to
> > modify it, as i've been able to do
> > in the past.  i don't know what i 
> > did to make it r/o.  
> > 
> > (permissions = 666)
> > 
> > $ ls -la .muttrc
> 
> $ chmod 644 .muttrc
> 
> > -rw-rw-rw-    1 bt       bt           8503 Oct 31 00:13 .muttrc
> 
> It should not be world writable
> 
> > 
> > (i am user "bt," so i am in the group.)
> > 
> > $ groups
> > 
> > bt mail cdrom floppy audio dip postgres
> > 
> 
> you do not need bt to be a member of mail (It does not harm,... I
> guess.)
> 
> > help is appreciated.
> 
> Cheers :)
> -- 
> ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
>         Osamu Aoki <osamu@debian.org>   Cupertino CA USA, GPG-key: A8061F32
>  .''`.  Debian Reference: post-installation user's guide for non-developers
>  : :' : http://qref.sf.net and http://people.debian.org/~osamu
>  `. `'  "Our Priorities are Our Users and Free Software" --- Social Contract
>

//

...oops, sorry about the "world writeable."
(the three 6's should've tipped me off.
whew!)  thx for the heads-up.

anyway, i'm able to save changes to the file 
_if_ i use the "!" to the command, ":wq".  i
guess the file is locked because it's a "hid-
den" file?  (the message i get after vi 
.muttrc is, ".muttrc already locked, session
is read-only.")  my non-"dot" files don't 
say that when massaged with nvi.  and i can
save them without the "!".

so, at least i can save file changes, which
basically consisted of adding this debian
list to .muttrc (subscribe debian-user@lists.
debian.org).  there was a recent thread chid-
ing users that reply to the list who also end
up sending a duplicate to a previous author 
in a thread.  and, besides, i don't want to 
get on madduck's bad side.  

i think my situation is resolved, or at least
i have a decent workaround.

thx to all respondents.

b.

//  
from me (pursuant to a recent thread by madduck).



Reply to: