From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Box cursor at EoL
Date: Fri, 7 Oct 2022 16:56:52 +0200 [thread overview]
Message-ID: <25408.15924.69822.546181@tux.local> (raw)
In-Reply-To: Msg <83pmf3opll.fsf@gnu.org> of 2022-10-07 14:11:34 +0300 from eliz@gnu.org
Eli,
On Friday, 2022-10-07 14:11:34 +0300, you wrote:
> ...
> > Well, I'm rarely using windows, normally I would open the same file in a
> > different frame, so the question arises: is there such a concept as a
> > FRAME-local variable?
>
> Yes: frame parameters can be used to that effect.
Ok, so I changed my hook function to
(lambda () (while-no-input
(set-frame-parameter nil ; Current frame.
'cursor-type ; Variable name.
(if (eolp) EoL-Cursor ; EoL value.
Cursor ; Nrm value.
) ) ) )
That works in different frames, but of course not in different windows
within the same frame. However replacing function `set-frame-parameter´
with `set-window-parameter´ prevented the hook function from working at
all, so `cursor-type´ doesn't seem to be a legal window parameter :-(
Can't I use window parameters to store cursor specific information?
Sincerely,
Rainer
next prev parent reply other threads:[~2022-10-07 14:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 15:16 Box cursor at EoL Dr Rainer Woitok
2022-10-05 15:34 ` Marcus Harnisch
2022-10-06 15:53 ` Dr Rainer Woitok
2022-10-06 17:00 ` Marcus Harnisch
2022-10-06 19:34 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-06 20:09 ` Marcus Harnisch
2022-10-07 8:28 ` Dr Rainer Woitok
2022-10-07 11:11 ` Eli Zaretskii
2022-10-07 13:49 ` Robert Pluim
2022-10-07 14:56 ` Dr Rainer Woitok [this message]
2022-10-07 15:37 ` Eli Zaretskii
2022-10-08 9:03 ` Dr Rainer Woitok
2022-10-08 9:12 ` Eli Zaretskii
2022-10-08 9:37 ` Dr Rainer Woitok
2022-10-08 10:13 ` Eli Zaretskii
2022-10-08 13:18 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-09 15:31 ` Dr Rainer Woitok
2022-10-05 16:53 ` Eli Zaretskii
2022-10-05 23:44 ` Emanuel Berg
2022-10-17 3:34 ` Kenneth Goldman
2022-10-17 4:06 ` Emanuel Berg
2022-10-18 17:06 ` Kenneth Goldman
2022-10-18 23:07 ` Emanuel Berg
2022-10-06 16:02 ` Dr Rainer Woitok
2022-10-05 23:44 ` Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
2022-10-18 8:29 Anders Munch
2022-10-18 10:22 ` Colin Baxter
2022-10-18 23:28 ` Emanuel Berg
2022-10-18 23:02 ` Emanuel Berg
2022-10-18 10:54 Anders Munch
2022-10-18 11:21 ` Colin Baxter
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=25408.15924.69822.546181@tux.local \
--to=rainer.woitok@gmail.com \
--cc=eliz@gnu.org \
--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).