From: Jeroen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Jeroen <contextntg@gmail.com>
Subject: Re: [NTG-context] Moving up a Figure
Date: Tue, 6 Jun 2023 19:39:46 +0200 [thread overview]
Message-ID: <CAPtmdbOzviSeyuhFk6C4oeCWq3QcNT_U1KiF3J_5Rzy9ozsBsg@mail.gmail.com> (raw)
In-Reply-To: <4n9p5qs0-6on6-83o9-snrr-1931n168nop6@hzvpu.rqh>
[-- Attachment #1.1: Type: text/plain, Size: 1674 bytes --]
This one works very nicely, though the movesidefloat gives nicely complete
control.
\samplefile{tufte}
\startplacefigure
[location={right,halfline},
number=no]
\externalfigure[autocad.png][width=0.6\textwidth]
\stopplacefigure
\samplefile{tufte}
Below the figure there is quite some space before the first line of text
starts, is there a way for the next text line to start immediately below
the future?
Op ma 5 jun 2023 om 19:38 schreef Aditya Mahajan via ntg-context <
ntg-context@ntg.nl>:
> On Mon, 5 Jun 2023, Alan Braslau via ntg-context wrote:
>
> > On 05/06/23 05/06/23, 00:08, Mikael Sundqvist via ntg-context wrote:
> > > On Mon, Jun 5, 2023 at 4:03 AM Jeroen via ntg-context
> > > <ntg-context@ntg.nl> wrote:
> > >> Not fully, it indeed moves up the figure but a little too much. Is
> there a
> > >> more granular method?
> > > Not that I know of, but maybe {right,halfline} will do?
> >
> > Maybe try "location={right,-1*hang},"
>
> For finer control, you can use `\movesidefloat`:
>
> \movesidefloat[x=-..., y=...]
> \startplacefigure
> [..]
> \stopplacefigure
>
> Aditya
>
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 2702 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-06-06 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 16:35 Jeroen via ntg-context
2023-06-03 18:22 ` Mikael Sundqvist via ntg-context
2023-06-05 2:02 ` Jeroen via ntg-context
2023-06-05 6:08 ` Mikael Sundqvist via ntg-context
2023-06-05 13:12 ` Alan Braslau via ntg-context
2023-06-05 17:36 ` Aditya Mahajan via ntg-context
2023-06-06 17:39 ` Jeroen via ntg-context [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPtmdbOzviSeyuhFk6C4oeCWq3QcNT_U1KiF3J_5Rzy9ozsBsg@mail.gmail.com \
--to=ntg-context@ntg.nl \
--cc=contextntg@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 NNTP newsgroup(s).