unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Heime <heimeborgia@protonmail.com>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: Heime via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Subject: Re: Printing alist pairs to a dedicated buffur
Date: Sat, 20 Apr 2024 16:37:12 +0000	[thread overview]
Message-ID: <V18Oxj_t3DY_tkMcEW26oPa7DKKsS_Ed0MZFn6sFcOmpWrGb08FFjsuSYd2LhmXLtpBnWEw4CvoGobfdBihg9aMDrTihFM_OVhzBo3JVt-8=@protonmail.com> (raw)
In-Reply-To: <87plukbbod.fsf@ledu-giraud.fr>


On Saturday, April 20th, 2024 at 9:55 PM, Manuel Giraud <manuel@ledu-giraud.fr> wrote:

> Heime heimeborgia@protonmail.com writes:
> 
> > This is how I am filling my alist named tema-lugar
> > 
> > (defun tema-mark (kfrz)
> > "Associate line number at cursor position with key phrase KFRZ."
> > (interactive "sString: ")
> > 
> > (let ( (lnum (line-number-at-pos)) )
> > 
> > (setq-local tema-lugar
> > (append tema-lugar
> > (list (cons kfrz lnum)))) ))
> 
> 
> Hi,
> 
> Maybe your error comes from this `setq-local'. I have used` defvar'
> which will create a global (i.e. visible everywhere in Emacs) variable.
> `setq-local' or` defvar-local' are used for buffer-local variables.
> Buffer-local variables are visible only from the buffer they were
> created.
> 
> In your previous command, the first thing you did was to switch to
> another buffer that knows nothing about tema-lugar. I suggest you to
> read "(elisp) Buffer-Local Variables". -> Manuel Giraud

Correct I have defined the alist with setq-local for information about the current
buffer.  And I want to print the contents of the alist to a buffer named "tika".




  parent reply	other threads:[~2024-04-20 16:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-19 12:57 Printing alist pairs to a dedicated buffur Heime
2024-04-19 13:24 ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-04-19 19:26   ` Heime
2024-04-19 19:42     ` Heime
2024-04-20  9:55       ` Manuel Giraud via Users list for the GNU Emacs text editor
2024-04-20 10:08         ` Emanuel Berg
2024-04-25 11:13           ` Heime
2024-04-26  0:27             ` Emanuel Berg
2024-04-25 15:55           ` [External] : " Drew Adams
2024-04-25 16:18             ` Heime
2024-04-25 22:43               ` Emanuel Berg
2024-04-25 22:29             ` Emanuel Berg
2024-04-25 23:38               ` Drew Adams
2024-04-26  0:03                 ` Emanuel Berg
2024-04-26 15:55                   ` Drew Adams
2024-04-26 16:57                     ` Heime
2024-04-26 17:27                       ` Yuri Khan
2024-04-27 22:20                         ` Heime
2024-04-26  0:41                 ` Emanuel Berg
2024-04-26  1:08                 ` Emanuel Berg
2024-04-20 16:37         ` Heime [this message]
2024-04-20 17:23           ` Heime
2024-04-20 20:48             ` Yuri Khan

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='V18Oxj_t3DY_tkMcEW26oPa7DKKsS_Ed0MZFn6sFcOmpWrGb08FFjsuSYd2LhmXLtpBnWEw4CvoGobfdBihg9aMDrTihFM_OVhzBo3JVt-8=@protonmail.com' \
    --to=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=manuel@ledu-giraud.fr \
    /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).