unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: drmemory@starband.net (DrMemory)
Subject: Re: emacsclient: controlling from an application?
Date: Fri, 17 Oct 2003 22:45:39 GMT	[thread overview]
Message-ID: <Ii_jb.1957$mH.498787437@twister1.starband.net> (raw)
In-Reply-To: jwv3cduz01j.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca

It was suggested that I set the auto-save-visited-file-name var:

>>You can set any variable on a per-buffer basis:
>>
>>(set (make-local-variable 'auto-save-visited-file-name) t)
>>
>>Try putting that in the file itself, either as the first line
>>
>># -*- eval: (set ...) -*-
>>

Which didn't work:

>> It appears that the eval worked:
>> However, the auto-save is still behaving as if the global value were in force:

And you suggested:

>
>The variable is consulted when visiting a file to setup some other
>auto-save-related variables.  What is probably occuring is that the
>variable is consulted before it is changed by the "eval: (set ...)"
>cookie.
>

Nosing around, I find a variable called buffer-auto-save-file-name.
Setting that in an eval statement does work, if anyone is
interested....

-*- eval: (setq buffer-auto-save-file-name "Whatever") -*-

Also, the run-with-idle-timer idea worked just fine. Thanks! Now I
just wish I could make the USR1 signal work. I'm running version
20.6.1 here at work, so I will try with my newer version at home
before submitting any bug reports...

  reply	other threads:[~2003-10-17 22:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 17:41 emacsclient: controlling from an application? DrMemory
2003-10-15 18:24 ` Stefan Monnier
2003-10-15 18:44   ` Stefan Monnier
2003-10-15 19:03     ` Stefan Monnier
2003-10-15 21:58   ` DrMemory
2003-10-16 15:17     ` Kevin Rodgers
2003-10-16 16:48       ` DrMemory
2003-10-16 19:00         ` Stefan Monnier
2003-10-15 18:25 ` Kevin Rodgers
2003-10-15 20:36   ` DrMemory
2003-10-15 21:04     ` Stefan Monnier
2003-10-17 22:45       ` DrMemory [this message]
2003-10-20 16:58         ` Kevin Rodgers
2003-10-15 20:46 ` DrMemory
2003-10-15 20:57   ` DrMemory
2003-12-01 21:40 ` Kai Grossjohann

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='Ii_jb.1957$mH.498787437@twister1.starband.net' \
    --to=drmemory@starband.net \
    /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).