emacs-devel
[Top][All Lists]
Advanced

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

address@hidden: custom-set-variables overwritten by safe-local-variables


From: Richard Stallman
Subject: address@hidden: custom-set-variables overwritten by safe-local-variables]
Date: Fri, 28 Apr 2006 11:45:27 -0400

Would someone please DTRT, then ack?

------- Start of forwarded message -------
From: Ralf Angeli <address@hidden>
To: address@hidden
Date: Thu, 27 Apr 2006 23:44:48 +0200
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
Subject: custom-set-variables overwritten by safe-local-variables
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed 
        version=3.0.4

- --=-=-=

The following mail was originally sent to the AUCTeX mailing list.  I
can reproduce the problem with a build on GNU/Linux checked out today.


- --=-=-=
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Return-Path: <address@hidden>
Delivery-Date: Thu, 27 Apr 2006 13:53:38 +0200
Received-SPF: pass (mxeu12: domain of googlemail.com designates 66.249.82.192
        as permitted sender) client-ip=66.249.82.192;
        address@hidden; helo=xproxy.gmail.com;
Received: from [66.249.82.192] (helo=xproxy.gmail.com)
        by mx.kundenserver.de (node=mxeu12) with ESMTP (Nemesis),
        id 0MKrQq-1FZ53v2ATY-0000rV for address@hidden;
        Thu, 27 Apr 2006 13:53:37 +0200
Received: by xproxy.gmail.com with SMTP id h30so1667599wxd
        for <address@hidden>; Thu, 27 Apr 2006 04:53:34 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com;
        
h=received:message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        
b=ippd+8qSagv5UO0TcNEWlPzIySeMCVdQyWpC6JWZEONkSZZILKT52snURhylwvz004wWDn+IdIFjfnlCdcb00phPruZEwcTI3VqlrPn6jmL+jthx4TTf46c5n9shugBC1OBgul4kzSO+M697uq5wr5LIvOronMvF49tywvTV5nk=
Received: by 10.70.105.7 with SMTP id d7mr1946161wxc;
        Thu, 27 Apr 2006 04:53:34 -0700 (PDT)
Received: by 10.70.54.16 with HTTP; Thu, 27 Apr 2006 04:53:34 -0700 (PDT)
Message-ID: <address@hidden>
Date: Thu, 27 Apr 2006 13:53:34 +0200
From: "Rainer Thiel" <address@hidden>
Reply-To: address@hidden
Sender: address@hidden
To: "Ralf Angeli" <address@hidden>
Subject: Re: [AUCTeX] another Problem with recent emacs + auctex packages
Cc: address@hidden
In-Reply-To: <address@hidden>
References: <address@hidden>
        <address@hidden>
Envelope-To: address@hidden
X-SpamScore: 0
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

2006/4/26, Ralf Angeli <address@hidden>:
> Can you provide a precise test case showing this behavior?  The test
> case should include an exact description of what you are doing, the
> .emacs file before and after you marked the variables as being secure.

I was not very precise indeed.  I was referring to messages like:

     > The local variables list in Kap.tex
     > contains values that may not be safe (*).
     >
     > Do you want to apply it?  You can type
     >
     > y  -- to apply the local variables list.
     > n  -- to ignore the local variables list.
     > !  -- to apply the local variables list, and
     >      mark these values (*) as
     >      safe (in the future, they can be set
     >      automatically.)
     >
     >    * TeX-Master: main.tex

that I got when loading .tex-files like

          >          \section{\"Uberschrift}
          >
          >          Etwas Text.
          >
          >               % Local Variables:
          >               % TeX-master: "main.tex"
          >               % End:

to point auctex to a TeX-master-file such as

          >          \documentclass{article}
          >          \begin{document}
          >          \include{Kap}
          >          \end{document}

I had not got any such message in previous emacs+auctex Versions.

I now see that the problem most certainly is related not to auctex, but
to todo (part of the calendar package).

In case anyone might be interested and able and willing to help all the
same, this is my problem description:

1. I invoke emacs (as in emacs+auctex-w32-2006-03-09.zip) with
   .emacs.el and no .todo-do file in my homedirectory, .emacs.el
   having the following content:

; .emacs.el START
; Time-stamp: <2006-04-27 11:52:16 Rainer Thiel>

         (autoload 'todo-mode "todo-mode"
                   "Major mode for editing TODO lists." t)
         (autoload 'todo-show "todo-mode"
                   "Show TODO items." t)
         (autoload 'todo-insert-item "todo-mode"
                   "Add TODO item." t)

(setq european-calendar-style t) ; oben schon definiert
(setq number-of-diary-entries 14) ; Anzahl der Tage fuer diary
                                  ; ohne Argument

(diary)        ; diary und todo-Liste bei Start anzeigen; deshalb muss
(todo-show)    ; european-calendar-style und number-of-diary-entries
;;             ; schon vorher definiert sein


(custom-set-variables
  ;; custom-set-variables was added by Custom.
  ;; If you edit it by hand, you could mess it up, so be careful.
  ;; Your init file should contain only one such instance.
  ;; If there is more than one, they won't work right.
 '(fill-column 72)
 )

; .emacs.el END

- --> emacs starts as exspected

2. I press M-x todo-insert-item and create a todo entry in the [Todo] category.
- --> todo creates .todo-do and .todo-top in my home directory

3. I leave emacs

4. I re-start emacs
- --> the following message is being displayed:

     > The local variables list in .todo-do
     > contains values that may not be safe (*).
     >
     > Do you want to apply it?  You can type
     >
     > y  -- to apply the local variables list.
     > n  -- to ignore the local variables list.
     > !  -- to apply the local variables list, and
     >      mark these values (*) as
     >      safe (in the future, they can be set
     >      automatically.)
     >
     >    * todo-categories : (Todo Todo Todo)

5. I type `!'
- --> .emacs.el is changed as follows:

; .emacs.el START
; Time-stamp: <2006-04-27 12:03:35 Rainer Thiel>

         (autoload 'todo-mode "todo-mode"
                   "Major mode for editing TODO lists." t)
         (autoload 'todo-show "todo-mode"
                   "Show TODO items." t)
         (autoload 'todo-insert-item "todo-mode"
                   "Add TODO item." t)

(setq european-calendar-style t) ; oben schon definiert
(setq number-of-diary-entries 14) ; Anzahl der Tage fuer diary
                                  ; ohne Argument

(diary)        ; diary und todo-Liste bei Start anzeigen; deshalb muss
(todo-show)    ; european-calendar-style und number-of-diary-entries
;;             ; schon vorher definiert sein
;; ;--------------------------------------------------------------------


(custom-set-variables
  ;; custom-set-variables was added by Custom.
  ;; If you edit it by hand, you could mess it up, so be careful.
  ;; Your init file should contain only one such instance.
  ;; If there is more than one, they won't work right.
 '(safe-local-variable-values (quote ((todo-categories "Todo" "Todo" "Todo")))))
; .emacs.el END

As is obvious, the line declaring the values as safe replaces the line
defining the fill-column instead of simply being added.  It also
doesn't have the desired effect, in that emacs asks about the unsafe
variable every time it is started.

When, on the other hand, todo is disabled, marking Local variables in
TeX-Files works as expected.

I have now disabled todo.

Many thanks again, also in advance

R.
- --
Prof. Dr. Rainer Thiel
Altertumswiss., Lehrstuhl Gr├Ązistik
07737 Jena, Germany (EU)
address@hidden

- --=-=-=
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
emacs-pretest-bug mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug

- --=-=-=--
------- End of forwarded message -------




reply via email to

[Prev in Thread] Current Thread [Next in Thread]