[Top][All Lists]

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

Re: 21.x feature request: windows shortcut support

From: David Masterson
Subject: Re: 21.x feature request: windows shortcut support
Date: 15 Oct 2001 16:04:53 -0700
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7

>>>>> Eli Zaretskii writes:

>> From: David Masterson <address@hidden>
>> Newsgroups: gnu.emacs.bug
>> Date: 15 Oct 2001 09:31:32 -0700
>> With respect to opening a shortcut, does Emacs keep any side-lists of
>> information about the files that it opens?  Could Emacs resolve the
>> shortcut and stuff the above information into such a "side-list"?

> Emacs doesn't track the files at all, it only tracks buffers.  When
> Emacs visits a file, it opens the file, read its contents into a
> buffer, then immediately closes the file and forgets about it.  Only
> the file's name and some other information (e.g., time it was visited)
> is kept as part of the buffer object.

How much "other information" is there?  Is that "other information"
kept as a list?  Could more information as necessary be hung off it?

After Emacs opens the file and loads the list, other functions (like
after-find-file) or hooks (like after-* hooks) can decide what to do
with the info.  For instance, after-find-file could take the file
referred to and do a find-alternate-file if read-thru-shortcutp is 't'
whereas, if it's 'nil, it would process auto-mode-alist against the
"*.lnk" file which might startup a shortcut-edit-mode.

The other area where I could see Emacs running into a shortcut is in
trying to execute a subprogram.  In this case, if it was asked to run
a program "X" and it determined (by checking a list of file types)
that "X" was "X.lnk", then it could just "Start X.lnk" and let Windows
handle the rest.

David Masterson                dmaster AT synopsys DOT com
Sr. R&D Engineer               Synopsys, Inc.
Software Engineering           Sunnyvale, CA

reply via email to

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