unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: tpeplt <tpeplt@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: Get buffer unto a new frame
Date: Sat, 26 Aug 2023 11:22:11 +0200	[thread overview]
Message-ID: <ZOnEQxwEGl3tDyMO@tuxteam.de> (raw)
In-Reply-To: <CAP_d_8U9+EOqz4dCp57xeUB4GGa0J6Ek00FD6LBqLNUs7BWPOg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]

On Sat, Aug 26, 2023 at 03:28:52PM +0700, Yuri Khan wrote:
> On Sat, 26 Aug 2023 at 03:24, tpeplt <tpeplt@gmail.com> wrote:
> 
> > I was hoping that there was a tool that
> > allowed for descriptions of the diagram elements instead of a
> > keyboard/mouse WYSIWYG tool.  This would allow a user to describe the
> > diagram elements and connections and would then generate the diagram.
> 
> The closest are Graphviz and PlantUML, but they render into SVG and
> not plain text, so I don’t reach for them when doing a small simple
> diagram in an email, a Reddit post, or a code comment.
> 
> Graphviz, in addition, is so low level that on many occasions I’ve
> wanted it generated from a higher-level description language rather
> than to write it directly.

Besides, Graphviz is extremely specialised: its emphasis is in
finding positions for its nodes and edges, which is absolutely
great if you can't or won't do it yourself but sucks if you
either want to convey some information via that positioning or
even if your pic doesn't consist of "nodes and edges" in the
first place.

The nicest "algorithmic" graphics package I know of is PGF/TiKZ [1],
but hey, it's a beast.

Cheers

[1] https://texample.net/tikz/
-- 
t

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2023-08-26  9:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  9:59 Get buffer unto a new frame Heime
2023-08-18 10:56 ` Christopher Dimech
2023-08-18 13:08   ` Tassilo Horn
2023-08-18 13:12 ` Yuri Khan
2023-08-18 13:41   ` Heime
2023-08-18 13:57     ` PierGianLuca
2023-08-18 14:10       ` Heime
2023-08-18 14:33         ` [External] : " Drew Adams
2023-08-18 14:36         ` PierGianLuca
2023-08-18 16:38           ` Yuri Khan
2023-08-24 16:01   ` tpeplt
2023-08-24 16:13     ` Corwin Brust
2023-08-24 16:20     ` Yuri Khan
2023-08-24 17:23       ` Richard Kerry via Users list for the GNU Emacs text editor
2023-08-25 20:24       ` tpeplt
2023-08-26  5:41         ` tomas
2023-08-26  8:28         ` Yuri Khan
2023-08-26  9:22           ` tomas [this message]

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=ZOnEQxwEGl3tDyMO@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tpeplt@gmail.com \
    --cc=yuri.v.khan@gmail.com \
    /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).