unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "समीर सिंह Sameer Singh" <lumarzeli30@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Implementing Vertical Text support in Emacs
Date: Sun, 20 Nov 2022 16:48:31 +0530	[thread overview]
Message-ID: <CAOR1sLyW5Ak6BX=kG8RBviWM1gt1D2v0fmCF8Yhx8sa-=uyqjA@mail.gmail.com> (raw)
In-Reply-To: <83v8p5e5mt.fsf@gnu.org>

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

I tried writing a vertical version of the display_line function but could
not get it to work. Emacs does not display any character after these
changes.
(maybe I should have also rewrote move_it_in_display_line_to?)

Therefore forgive me for asking again, if for now I just want to make the
characters appear column wise instead of row wise, disregarding line
overflow, or termination of a line etc,
do I still have to look into the display_line function, because as I recall
I had once removed most of the lines of the display_line function and Emacs
was still displaying lines fines.

Again, thank you for your patience.

On Fri, Sep 30, 2022 at 12:00 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: समीर सिंह Sameer Singh <lumarzeli30@gmail.com>
> > Date: Fri, 30 Sep 2022 01:27:01 +0530
> > Cc: emacs-devel@gnu.org
> >
> >  Before you modify display_line, you need to decide how will the
> >  vertical-layout display produce glyphs.
> >
> > Can you please expand more on this?
> > How to produce glyphs in a column wise order?
>
> I did that in the original message.  Quoting myself:
>
>   Before you modify display_line, you need to decide how will the
>   vertical-layout display produce glyphs.  The easiest would be to
>   produce them in column-wise order, because that basically processes
>   the buffer in the order of character positions, like Emacs does now.
>   This will allow you to leave the lower levels, which walk the buffer
>   and deliver characters, mostly intact.
>
>   So perhaps you should have a display_column function, which will look
>   like display_line, but instead of advancing the X coordinate, it will
>   advance the Y coordinate, and produce a single column, top to bottom.
>   Then the basic calculations should be the same as in display_line,
>   except the column ends when it reaches last_visible_y instead of
>   last_visible_x.  IOW, the glyph matrices will be made of glyph columns
>   instead of glyph rows.  Basically, the roles of the X and the Y
>   coordinates will be swapped.
>
> > I looked at gui_produce_glyphs and that led me to append_glyph, but I
> could not figure out how the glyphs are
> > produced.
> > There is also draw_glyphs but I think working with that will require
> editing the low level *term files (if it even is
> > the right function)
>
> I didn't mean gui_produce_glyphs and its subroutines, I mean the logic
> of how glyphs are produced, as described above, in display_line
> itself.  The current code in display_line produces glyph of a single
> screen line, in visual order, from left to right.  Above I suggested
> to write a similar display_column function, which will produce glyphs
> of a single column, top to bottom, and will make the decisions
> regarding when the column is full and should be terminated, like
> display_line does with respect to screen lines.  Does this sounds like
> a good approach to you?
>
> If the approach sounds good, but something in my description is
> unclear, please ask more specific questions about those unclear parts
> of what I wrote.
>

[-- Attachment #2: Type: text/html, Size: 3771 bytes --]

  reply	other threads:[~2022-11-20 11:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 15:29 Implementing Vertical Text support in Emacs समीर सिंह Sameer Singh
2022-06-13 16:16 ` [External] : " Drew Adams
2022-06-13 16:30 ` Eli Zaretskii
2022-06-15 10:08   ` Richard Stallman
2022-06-15 10:22     ` Po Lu
2022-06-15 11:09       ` समीर सिंह Sameer Singh
2022-06-16 22:48         ` Richard Stallman
2022-06-17  1:43           ` समीर सिंह Sameer Singh
2022-06-17  6:12             ` Eli Zaretskii
2022-09-08 18:44               ` समीर सिंह Sameer Singh
2022-09-08 19:05                 ` Eli Zaretskii
2022-09-10 15:53                   ` समीर सिंह Sameer Singh
2022-09-10 16:17                     ` Eli Zaretskii
2022-09-29 19:57                       ` समीर सिंह Sameer Singh
2022-09-30  6:30                         ` Eli Zaretskii
2022-11-20 11:18                           ` समीर सिंह Sameer Singh [this message]
2022-11-20 11:43                             ` Eli Zaretskii
2022-11-20 12:08                               ` समीर सिंह Sameer Singh
2022-11-24 11:39                                 ` Eli Zaretskii

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='CAOR1sLyW5Ak6BX=kG8RBviWM1gt1D2v0fmCF8Yhx8sa-=uyqjA@mail.gmail.com' \
    --to=lumarzeli30@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).