[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#28350: enriched.el code execution
From: |
Eli Zaretskii |
Subject: |
bug#28350: enriched.el code execution |
Date: |
Thu, 07 Sep 2017 05:34:34 +0300 |
> Date: Wed, 06 Sep 2017 21:25:18 +0200
> From: charles@aurox.ch (Charles A. Roelli)
>
> As for a fix to apply to master: I'd like to keep "x-display" if we
> can agree on some "safe" predicate that the given parameter would have
> to satisfy. Looking at the list of display specifications that are
> available, it seems that simple string, margin text, space-width,
> height (only in the (+ n), (- n) and n cases) and raise specifications
> should be okay. Does anybody else have an opinion about this?
I agree that the cases you have shown are safe.
Thanks.
- bug#28350: enriched.el code execution, Charles A. Roelli, 2017/09/04
- bug#28350: enriched.el code execution, Charles A. Roelli, 2017/09/06
- bug#28350: enriched.el code execution,
Eli Zaretskii <=
- bug#28350: enriched.el code execution, Charles A. Roelli, 2017/09/09
- bug#28350: enriched.el code execution, Eli Zaretskii, 2017/09/09
- bug#28350: enriched.el code execution, Charles A. Roelli, 2017/09/09
- bug#28350: enriched.el code execution, Eli Zaretskii, 2017/09/09
- bug#28350: enriched.el code execution, Charles A. Roelli, 2017/09/09
- bug#28350: enriched.el code execution, Eli Zaretskii, 2017/09/10
- bug#28350: enriched.el code execution, Glenn Morris, 2017/09/11
- bug#28350: enriched.el code execution, Eli Zaretskii, 2017/09/11
bug#28350: enriched.el code execution, Paul Eggert, 2017/09/09