From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id 8PtnBtwbqmV7zgAAe85BDQ:P1 (envelope-from ) for ; Fri, 19 Jan 2024 07:51:08 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id 8PtnBtwbqmV7zgAAe85BDQ (envelope-from ) for ; Fri, 19 Jan 2024 07:51:08 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=L2qqz5sp; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1705647068; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=7oTzyI+MU30bmeEkpYhymSzf2PJHvVM+bwSDXiOIVYs=; b=uqqNWZ0hSP9TvOMqfLdGtvo7F/DiNX8SnRPKpRlRnoB8165hZGmL9HbgFYs4HVv6BzIzzD RZ8NIvpyfmeheT7queuGCDM7LnLl/R9sDEwiNKYRpKjOpBbEQgWIuX0FIU6nWWMUeICUm0 N6c07SGEPvQD+VTEoM27XCw+/9GNjt9Ib6MrXjzDhfO8iXxJBjFDiGRFJX9M+vhM2hTJVz g+B2/zpg1X5xLnzs8m/MaQ5Fg6XPBNqToY/Yr/+qJY6EkRQ7FJmAq/VEXgTuDTF7gYF8Ig +O1rtUEOwPl98DWDyir7VZKJvBqf026bfx+8D630kF3AKynfzMV7paPs7Mf8Qg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=L2qqz5sp; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1705647068; a=rsa-sha256; cv=none; b=HNN7MK4+x5r/Ojf/gJFEIbXaLAZkoQCxkA4hvkFSA8rxvesOfCNpyOL4bdcd+3h8N7B59X ig7OpMoXoG3SQ5hU8UKoHNUpeGu4P+ZMyLNocqTTBLcpADuVS6hx70RYxDBPcPReSbgWOH sfuHp1IciM4jvcxgB+04CE+xXxiSDaaDZqI0jh3qihiZGd2yVZKGDa8qTOIgttAljKLaJB 0hNbpu6FcasWRx1p8P2lMqrswTYI6HY5IbcGdgBq/HbwK+ndeNCfRtWbd3HCNggYtJXuFE IUe6D8ZjWeXnXAgJRiJYNN2KG8Cm+mEwAV25dmzHIYF9+nWWq3VZEFb91Jbmiw== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id C59696B68A for ; Fri, 19 Jan 2024 07:51:07 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rQihf-0002b6-8n; Fri, 19 Jan 2024 01:50:11 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rQihd-0002au-I0 for emacs-orgmode@gnu.org; Fri, 19 Jan 2024 01:50:09 -0500 Received: from mail-wm1-x32d.google.com ([2a00:1450:4864:20::32d]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rQihb-0001k0-HU for emacs-orgmode@gnu.org; Fri, 19 Jan 2024 01:50:09 -0500 Received: by mail-wm1-x32d.google.com with SMTP id 5b1f17b1804b1-40e8fec0968so5647525e9.1 for ; Thu, 18 Jan 2024 22:50:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705647005; x=1706251805; darn=gnu.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=7oTzyI+MU30bmeEkpYhymSzf2PJHvVM+bwSDXiOIVYs=; b=L2qqz5spaU7T6DKFqkTHXdtJLx07ByjTZeOJ/AyMCgNDVqcVzykcqkGQK2GpA3uASJ YPfY+StDi74ajJku26ScYJnIcyCp8S34ohddOKggHBUTOvuEnke5gBUwLQPJFxoqz3oQ OOxcdHKE9ZHt77y7zJTdo8xc7/qiIpxW8EIpmM5orYT++/43ODRXnelZ+SJj5j/9Dx5Y HH3k5xlr7tmSa29i1P950jtiuWoo1shGyLiMr4GJBsMAqUA0/RLL3YqIsEzAD50Zmg4Y WLoAGCZlOii/RdbQt/wH7GFU/J6Q7ytRb8clIi5l2YPQO7AgGk7cL/u82Cg1OTSRffy3 TrGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705647005; x=1706251805; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=7oTzyI+MU30bmeEkpYhymSzf2PJHvVM+bwSDXiOIVYs=; b=IbEwmsdUKzq29e+xDsxBOlss9bTN9Rwe572ily4MAxs5o1OTtn1jYe+X2y+Rhh5vLB ZI29XWOJY3JiqHxnXdesBFx0VgIelH5BR9ioowHJmfR7iAKxBXgveR8WmsQszig6gD97 623R+XjX70YpJG7jWAfTbuGgDTXIqTSQw5LDmqccdr0rGfUEVqjbrONxGMCw36F90UDm tASDuaZsQeg0cywuQKxwsXWtbdJhfSWOCBzlheltaKIxqDduhg6s1E6b24pp2ijU/tDe VH6oulvWRMwSINIu3iAuMDBLRCK52t8mgD3SuirWxk6pid5ydn9h318CfilXotrj6q46 V3Dg== X-Gm-Message-State: AOJu0YzTaonj/4RoIdvisBFh1taV1DsYkyxKsjX6DxTA0iyud/61LsCp gM0oe3PVruhBwpGtY79iBCk+Jz8O8PgqXKroHukU8vMmvovpluRbaLLSklthtKHrOQpseAeJQTk Lj2w0FK+KxW+smqazJAUxMzvnaCKBGLIE X-Google-Smtp-Source: AGHT+IHcdi4sptKzZdxyUsWRcUzBI1cUMdSf24tHtrHMV0pyVSqTyDQjoZgMheiG+jInihl110AI2SAf5j8Nrde24wk= X-Received: by 2002:a05:600c:6a92:b0:40e:5ad1:5820 with SMTP id jl18-20020a05600c6a9200b0040e5ad15820mr1154252wmb.161.1705647005207; Thu, 18 Jan 2024 22:50:05 -0800 (PST) MIME-Version: 1.0 References: <87sfx8xjte.fsf@gmail.com> <87pmscxjgb.fsf@gmail.com> In-Reply-To: <87pmscxjgb.fsf@gmail.com> From: Matt Huszagh Date: Thu, 18 Jan 2024 22:49:54 -0800 Message-ID: Subject: Re: Patch to allow adjusting latex fragment display scale factor To: "emacs-orgmode@gnu.org" , Ihor Radchenko Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2a00:1450:4864:20::32d; envelope-from=huszaghmatt@gmail.com; helo=mail-wm1-x32d.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -6.99 X-Migadu-Queue-Id: C59696B68A X-Spam-Score: -6.99 X-Migadu-Scanner: mx11.migadu.com X-TUID: IynWfZJY1beT Hi, Bringing this back up. Ihor, I've added you to the thread directly (hope that's ok). Any thoughts? I have not yet updated it for the most recent changes to main, but I can do that. Matt On Sun, Oct 10, 2021 at 9:40=E2=80=AFPM Matt Huszagh wrote: > > Matt Huszagh writes: > > > I've created a patch to allow adjusting the scale factor used for inlin= e > > latex image fragments. This involves a customizable variable that can > > either be set to a scale factor (defaults to 1.0) or a function that > > evaluates to a scale factor. > > > > This feature is in addition to the existing scale factor adjustment > > capability provided by `org-preview-latex-process-alist' through > > `:image-size-adjust'. Wherease image-size-adjust performs scaling at th= e > > time of image generation, the new change performs it during > > display. This can lead to significant time saving and suffers no loss o= f > > quality for vector graphics. > > > > As an example of use, I have several functions for changing frame > > scaling. I've added > > > > (if (eq major-mode 'org-mode) > > (progn > > (org-clear-latex-preview) > > ;; 16 corresponds to the C-u C-u arg prefix. > > (org-latex-preview 16))) > > > > to these functions so that changing the frame scaling also > > correspondingly changes the latex preview/fragment scaling to match the > > new size of the surrounding text. Because of this new feature, this > > change is effectively instantaneous for reasonably numbers of > > overlays. Obviously, something similar could be done for > > `text-scale-adjust' (e.g., through `advice-add'). > > > > Feedback appreciated. > > Apologies, the patch I sent is slightly wrong. The line numbers also > reflect an earlier patch I made. Here is a corrected version. >