Hello,
The sed manual has been expanded
to discuss locale and invalid multybyte sequences,
incorporating some details from this thread.
See:
https://git.savannah.gnu.org/cgit/sed.git/commit/?id=05800ee0b7
regards,
- assaf
Hello,
Paolo Bonzini wrote:
On 22/07/2016 09:02, Daniel Iancu wrote:
sed -ni 's/foo/bar/' test # fails
So this is not a bug.
I've expanded sed's manual to mention this specific issue:
https://git.savannah.gnu.org/cgit/sed.git/commit/?id=a36e8abccc5db38e4d2f8ea2bbb3e78dfddacd78
regards,
-
Hello,
- it is not specified whether address selections following a command
act on unchanged input lines [...] or on the lines as changed by the
previous command
I've clarified this point in sed's manual and man-page:
https://git.savannah.gnu.org/cgit/sed.git/commit/?id=de6b6ccd7400b6483e
Hello,
I've added a paragraph about the current behavior
with your example to sed's manual:
https://git.savannah.gnu.org/cgit/sed.git/commit/?id=a805d57e1f6427b55
regards,
- assaf
Hello,
If it helps in any way, the documentation in sed-4.4 (included in
'stretch') as licensed under GFDLv1.3 and explicitly states:
"with no Invariant Sections, no Front-Cover Texts, and no
Back-Cover Texts."
http://git.savannah.gnu.org/cgit/sed.git/tree/doc/sed.texi#n39
regards,
- assa
Hello,
Panu Kalliokoski wrote:
However, the possibility of using semicolons in not mentioned on sed's
man page nor in its info document. Instead, both insist that every
command must be on its own line.
There's now a dedicated section
in gnu sed's manual about multiple commands and semicolons:
Hello,
- Usage of multiple commands [...]
- The possibility to use a semicolon instead of a newline [...]
12 years later, there's now a dedicated section
in gnu sed's manual about multiple commands and semicolons:
https://www.gnu.org/software/sed/manual/html_node/Multiple-commands-syntax.html
Hello,
Picking up an old sed bug:
Matija Nalis wrote:
echo 'a^c' | sed -e 's/\x5e/b/'
should produce output "abc" (as it does in "ssed" or "perl -pe"), but
in GNU sed it produces "ba^c".
I agree this is indeed GNU sed's behavior,
but it's not clear it is incorrect behavior (or if there is
Hello,
sed-4.4 with the segfault bugfix has been released:
https://lists.gnu.org/archive/html/info-gnu/2017-02/msg1.html
Available here:
https://ftp.gnu.org/gnu/sed/sed-4.4.tar.xz
regards,
- assaf
Package: sed
Version: 4.3-3
Severity: serious
Hello,
My name is Assaf, I'm a new co-maintainer of GNU Sed.
I'm writing to you about updates to 'sed-4.3' for the coming 'stretch'
release. A bug was discovered in sed-4.3 which can lead to a segfault.
We're working on releasing a bugfix release
Hello,
On 06/06/2015 06:13 AM, Gavin Smith wrote:
Looking at the dir file you attached, there are the following entries:
* Coreutils: (coreutils). Core GNU (file, text, shell) utilities.
* coreutils: (coreutils)coreutils invocation. Multi-call program.
The two labels are "Coreutils" an
On 09/09/2014 10:52 AM, Michael Stone wrote:
On Tue, Sep 09, 2014 at 03:31:35PM +0100, Pádraig Brady wrote:
It's useful to many, but I agree most don't bother with it
due to the awkward non intuitive default info reader _interface_
(though pinfo is a bit better in that regard).
Right. I've hea
012 at 04:21:29PM -0400, Assaf Gordon a écrit :
>>
>> I've created a new tarball which explicitly includes "unistd.h" in the
>> relevant CPP files - may I ask you to test it ?
>>
>> http://cancan.cshl.edu/labmembers/gordon/files/fastx_toolkit-0
Hello Charles,
Charles Plessy wrote, On 04/04/2012 12:17 AM:
>
> Debian distributes FASTX-Toolkit, and after a mass-rebuild against GCC 4.7, we
> noticed the following error:
>
> ../libfastx/sequence_alignment.h:146:32: error: 'ssize_t' does not name a
> type
>
I can't reproduce it locally
Hello Charles,
Charles Plessy wrote, On 05/21/2011 04:28 AM:
> It still fails to build on Ubuntu, with the error I silenced with the patch in
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626757#5
>
Please try this new version, available here:
http://hannonlab.cshl.edu/fastx_toolkit/libgtext
Charles,
I've put a fixed version here:
http://hannonlab.cshl.edu/fastx_toolkit/fastx_toolkit-0.0.13.1.tar.bz2
Please let me know if it solves the complication issue, then I'll make it
publicly available on the website.
-gordon
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.deb
Charles,
I've put a fixed version here:
http://hannonlab.cshl.edu/fastx_toolkit/libgtextutils-0.6.1.tar.bz2
Please let me know if it solves the complication issue, then I'll make it
publicly available on the website.
-gordon
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.
Sorry about the previous email (the "g++ fails sanity check") - it was my bad.
Should have used CXX instead of CPP shell variables.
I'm now able to compile libgtextutils using gcc/g++ version 4.6,
and I'm not seeing the error you are mentioning.
What should I change in order to reproduce the prob
Hi Charles,
I'm trying to fix it issue, perhaps you can help me with a strange compilation
problem:
I've installed a fresh VM of debian/testing and upgraded to unstable.
I've installed g++ 4.6 ( gcc version 4.6.1 20110428 (prerelease) (Debian
4.6.0-6 ) ).
When I run the "configure" of libgtexu
19 matches
Mail list logo
