A NOTE has been added to this issue. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1771 
====================================================================== 
Reported By:                calestyo
Assigned To:                
====================================================================== 
Project:                    Issue 8 drafts
Issue ID:                   1771
Category:                   Shell and Utilities
Type:                       Enhancement Request
Severity:                   Editorial
Priority:                   normal
Status:                     Resolved
Name:                       Christoph Anton Mitterer 
Organization:                
User Reference:              
Section:                    Utilities / printf 
Page Number:                3269 
Line Number:                111019 
Final Accepted Text:        See
https://www.austingroupbugs.net/view.php?id=1771#c6439. 
Resolution:                 Accepted As Marked
Fixed in Version:           
====================================================================== 
Date Submitted:             2023-08-07 19:22 UTC
Last Modified:              2023-09-01 01:40 UTC
====================================================================== 
Summary:                    support or reserve %q as printf-utility format
specifier
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0001774 Support ' <apostrophe> as a forma...
====================================================================== 

---------------------------------------------------------------------- 
 (0006444) kre (reporter) - 2023-09-01 01:40
 https://www.austingroupbugs.net/view.php?id=1771#c6444 
---------------------------------------------------------------------- 
On the general question of %q/%Q - I have an implementation for NetBSD's
printf, but there is no way I was ever going to implement the nonsense
that
is the bash %q (the way it uses the precision is absurd), so I never
bothered
to commit it (more  differing variants helps no-one, better just to not
have it at all).

I didn't know (until this discussion) that bash now has %Q - that looks
like
what I implemented, so now I might switch from %q to %Q and commit that.
That's a rational way to do things.

And wrt the printf(3) function chars that are available for use by
printf(1)
'v' and 'y' are not really candidates, as C might define those, but we can
usurp any of 'h' 'j' 'l' 'n' 'p' 't' and 'z' (and probably 'w').   I don't
know what 'k' and 'r' are intended to do, so perhaps those too.

None of those make any sense (as C defines them) for printf(1), none are
(in the standard) supported to mean anything at all, so we could give
meanings
to any of that set, for operations that printf(3) will never want to
perform,
should we so desire. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2023-08-07 19:22 calestyo       New Issue                                    
2023-08-07 19:22 calestyo       Name                      => Christoph Anton
Mitterer
2023-08-07 19:22 calestyo       Section                   => Utilities / printf
2023-08-07 19:22 calestyo       Page Number               => 3269            
2023-08-07 19:22 calestyo       Line Number               => 111019          
2023-08-07 19:36 chet_ramey     Note Added: 0006416                          
2023-08-07 19:46 calestyo       Note Added: 0006417                          
2023-08-07 23:39 salewski       Issue Monitored: salewski                    
2023-08-08 08:46 geoffclare     Note Added: 0006418                          
2023-08-08 14:28 calestyo       Note Added: 0006420                          
2023-08-08 15:04 geoffclare     Note Added: 0006421                          
2023-08-08 17:10 calestyo       Note Added: 0006422                          
2023-08-08 18:45 eblake         Note Added: 0006423                          
2023-08-08 20:40 jsm28          Note Added: 0006424                          
2023-08-08 20:53 calestyo       Note Added: 0006425                          
2023-08-31 16:10 Don Cragun     Note Added: 0006439                          
2023-08-31 16:13 Don Cragun     Final Accepted Text       => See
https://www.austingroupbugs.net/view.php?id=1771#c6439.
2023-08-31 16:13 Don Cragun     Status                   New => Resolved     
2023-08-31 16:13 Don Cragun     Resolution               Open => Accepted As
Marked
2023-08-31 16:14 Don Cragun     Tag Attached: issue8                         
2023-08-31 17:46 eblake         Relationship added       related to 0001774  
2023-08-31 17:48 eblake         Note Added: 0006440                          
2023-08-31 17:49 eblake         Note Edited: 0006440                         
2023-08-31 18:33 eblake         Note Added: 0006441                          
2023-08-31 22:00 eblake         Note Added: 0006442                          
2023-09-01 01:23 kre            Note Added: 0006443                          
2023-09-01 01:40 kre            Note Added: 0006444                          
======================================================================


  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group
  • [Issue 8 dra... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to