taskManeage - Tasks: task #15755, Citing CPU architecture in a macro...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #15755: Citing CPU architecture in a macro in the project

Submitted by:  Mohammadreza Khellat <mkhellat>
Submitted on:  Wed 19 Aug 2020 07:11:50 AM UTC  
 
Should Start On:  Wed 19 Aug 2020 12:00:00 AM UTC Should be Finished on:  Wed 19 Aug 2020 12:00:00 AM UTC
Category:  Software Priority:  5 - Normal
Status:  Done Privacy:  Public
Percent Complete:  100% Assigned to:  Mohammadreza Khellat <mkhellat>
Open/Closed:  Closed Effort:  0.00

Fri 28 Aug 2020 01:00:16 PM UTC, comment #4: 

Thanks for the clarifications Mohammad-reza.

Good point! Can you add those special characters ;-)?

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Fri 28 Aug 2020 12:56:01 PM UTC, comment #3: 

Thanks Mohammad for the corrections :)

Yeah, regarding filename limitations, at first I wanted to rule out the 20-22 unix shell special characters. But then I said to myself, maybe we can come up with a simpler convention by only allowing :alnum:, -, and /.

Anyways, the discussion around "filenames" is related to the filesystem specifications (specifically limitations) as well as shell internals when filenames are not stores as strings.

Just as a reference:
https://en.wikipedia.org/wiki/Comparison_of_file_systems
[apart from / and NUL, there are no limitations for ext2+ and btrfs. As for xfs and hpfs the only limitation is NUL].

Regarding shell special characters when filename is not stored as string, I think we should add the following characters to the list in the 'case' in Commit c6a4aaad62a9:

  • ~
  • |
  • `  (archaic)
  • [ , ]
  • ' , "
  • < , >
Mohammadreza Khellat <mkhellat>
Project MemberIn charge of this item.
Thu 27 Aug 2020 11:53:37 AM UTC, comment #2: 

Thanks a lot Mohammadreza, it has been merged into Maneage as Commit c6a4aaad62a9 :-).

This was an important piece of information and I am happy that Maneage users now have it as a LaTeX macro to use in their paper anywhere they want.

I just made some small corrections:

  • The 'clear' statement in '--check-config' is removed because in many cases, people want to compare with previous seconds (or just scroll up to see when a software was built).
  • I noticed that instead of searching for meta-characters, the commit was only limiting the build directory to have these characters: 0-9, a-z, A-Z, with '/' and '-'! This is very limited: for example people may have their directory names in different languages, or they commonly use characters like '_'. Generally, its good to specifically match with known problematic characters, not limit the user to very few of them ;-). So I corrected the check to only break if known problematic characters are present. We can easily add new problematic characters if anyone confronts a problem later ;-).
Mohammad Akhlaghi <makhlaghi>
Project Administrator
Wed 26 Aug 2020 12:19:40 PM UTC, comment #1: 

Good afternoon!
After 2-3 hours of discussion with Mohammad, the new changes for this can be found in
https://codeberg.org/mkhellat/maneage-mkhellat/src/branch/add_cpu_arch_macro

Please check and let me know if you found any issues.

Mohammadreza Khellat <mkhellat>
Project MemberIn charge of this item.
Wed 19 Aug 2020 07:11:50 AM UTC, original submission:  

Following the discussion in https://savannah.nongnu.org/task/?15741#comment9 [task #15741-comment9], it is important to document CPU architecture with which the project was built.

Mohammadreza Khellat <mkhellat>
Project MemberIn charge of this item.

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by makhlaghi (Posted a comment)
  • -email is unavailable- added by mkhellat (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-08-27 makhlaghi StatusIn Progress => Done
        Percent Complete80% => 100%
        Open/ClosedOpen => Closed
    2020-08-26 mkhellat Percent Complete0% => 80%

    Back to the top


    Powered by Savane 3.7