From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Welsh Duggan Newsgroups: gmane.emacs.devel Subject: Re: Display question Date: Thu, 09 Jun 2011 15:10:06 -0400 Message-ID: <8739jihldd.fsf@maru.md5i.com> References: <87hb80hno5.fsf@maru.md5i.com> <8339jkdam3.fsf@gnu.org> <87boy8h3f3.fsf@maru.md5i.com> <83zklsb8oc.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1307646651 5506 80.91.229.12 (9 Jun 2011 19:10:51 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 9 Jun 2011 19:10:51 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 09 21:10:47 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QUkcw-0007hx-O4 for ged-emacs-devel@m.gmane.org; Thu, 09 Jun 2011 21:10:46 +0200 Original-Received: from localhost ([::1]:39838 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QUkcv-0003oH-67 for ged-emacs-devel@m.gmane.org; Thu, 09 Jun 2011 15:10:45 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:47723) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QUkcT-0003nR-I8 for emacs-devel@gnu.org; Thu, 09 Jun 2011 15:10:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QUkcR-0000mQ-Hl for emacs-devel@gnu.org; Thu, 09 Jun 2011 15:10:17 -0400 Original-Received: from md5i.com ([75.151.244.229]:60591 helo=maru.md5i.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QUkcP-0000kR-78; Thu, 09 Jun 2011 15:10:13 -0400 Original-Received: from md5i by maru.md5i.com with local (Exim 4.76) (envelope-from ) id 1QUkcI-0003lx-P0; Thu, 09 Jun 2011 15:10:06 -0400 In-Reply-To: <83zklsb8oc.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 08 Jun 2011 19:16:19 +0300") User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 75.151.244.229 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:140331 Archived-At: Eli Zaretskii writes: >> From: Michael Welsh Duggan >> Date: Wed, 08 Jun 2011 09:13:20 -0400 >> Cc: emacs-devel@gnu.org >> >> (I was playing around with ideas on how to display and undisplay bidi control >> characters, as you might have guessed.) > > It might be a good idea to have a minor mode that would show the > directional formatting codes in such a human-readable form. Please > consider contributing such a mode. TIA. So, for the most part it looks like (update-glyphless-char-display 'glyphless-char-display-control '((format-control . acronym) (no-font . hex-code))) does what I want. But the nature of glyphless-char-display is that of a global variable, as opposed to a buffer-local variable, and making this variable buffer local and doing a vector-based copy-tree of the original doesn't cause a buffer-local effect. I don't know necessarily think that declaring glyphless-char-display with DEFVAR_PER_BUFFER is necessarily the right solution. Presumably it->object would be the buffer in question in lookup_glyphless_char_display, so getting the buffer local value would be possible, but honestly if we were to want to used the buffer local value, it should be cached at the beginning of the display of the buffer. Thoughts? -- Michael Welsh Duggan (md5i@md5i.com)